Hydration issues on serialized Model with relations

[liviuroman]

I have a problem that I can't figure out, and I'm not sure if it's a bug or if I don't understand how relationship model hydration works when they running from queue.

Some code as example:

app\Models\Author:

public function books(): HasMany
{
    return $this->hasMany(Book::class);
}

public function primaryGenreBooks(): HasMany
{
    return $this->hasMany(Book::class)->where('genre', $this->primary_genre);
}

app\Console\Commands\SendAuthorProcessingJob:

$author1 = Author::with(['books', 'primaryGenreBooks'])->first();
$author2 = Author::first();

ProcessAuthorJob::dispatch($author1);
ProcessAuthorJob::dispatch($author2);

app\Jobs\ProcessAuthorJob:

use SerializesModels;

public function __construct(public Author $author)

public function handle(): void
{
    dump($this->author->books);

    dump($this->author->primaryGenreBooks);
}

• scenario 1 when $author1 is dispatched: the "books" relation works (I got a Collection as a result), but "primaryGenreBooks" does not work (I got NULL as a result)
• scenario 2 when $author2 is dispatched: both relationships work properly (I got Collection as a result from both relations)

From what I have observed, in the first scenario, the "primaryGenreBooks" relationship does not work because $this in the relationship function is null.

I'm not really looking for a workaround, but for an explanation on what I'm missing and why is working like that.

[macropay-solutions]

Dispatching a model will only dispatch it's primary key and the model will be fetched in the job by primary key.
Possible solutions:
Dispatch array
or Move the queries in the jobs
or try to manually serialize them as payload.

You accessing the relations in the job will generate a new query for them.