Observer not triggering from a running job.

This is very odd, because the process for creating a model is still the same here. Can you show us how you store the post to the database in your listener?

Of course. So this is my Observer:

public function created(Post $post)
{
    dd('should run this');
}

and this is the Job:

public function handle(PostService $service) {
   ...
    var_dump('saving post to database...');
   $service->post(title, description, x, y, z);
}

and Service:

public static function post(title, description, x, y, z) {
    ...
    $post = Post::create([
                    'title' => $title,
                    'description' => $description,
                    'x' => $x,
                    'y' => $y,
        ]);
}

output from bash:

Processing: App\Jobs\Broker\Post
/var/www/app/Jobs/Broker/Post.php:119:
string(45) "saving post to database..."

And checking the database, I do indeed see the post I just created. new ID, created_at timestamp so I'm sure it's not an old one i'm looking at. but the dd() never runs. :(

do you see

Processed: App\Jobs\Broker\Post

Any errors in the log file?

No errors that I could see, and it does say Processed. However have since found this issue. I WAS killing the worker each time to ensure that the file rebuilt (any changes to a running worker will not be present until you restart the job queue). My docker container from the outside was telling me I had no running worker. By running docker top my_container I could see my worker disappearing when I ran artisan queue:restart.

However, when I logged directly in to the container using docker exec -it my_container bash it seemed it had left a rogue worker running in the background. I was unable to kill it, so I had to rebuild the container to stop it.

Once I had done that, the changes started showing, and the file started var dumping when expected.

Lessons to be learnt? If in doubt, take off and nuke the site from orbit.