Updating a client process can fail with a model not found exception

[lindyhopchris]

A ModelNotFoundException can be caused by the UpdateClientProcess listener, for example:

Illuminate\Database\Eloquent\ModelNotFoundException: No query results for model [App\Post].

/vagrant/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Builder.php:414
/vagrant/vendor/laravel/framework/src/Illuminate/Queue/SerializesAndRestoresModelIdentifiers.php:85
/vagrant/vendor/laravel/framework/src/Illuminate/Queue/SerializesAndRestoresModelIdentifiers.php:55
/vagrant/vendor/laravel/framework/src/Illuminate/Queue/SerializesModels.php:45
/vagrant/vendor/cloudcreativity/laravel-json-api/src/Queue/UpdateClientProcess.php:58
/vagrant/vendor/cloudcreativity/laravel-json-api/src/Queue/UpdateClientProcess.php:36

Encountered this in a scenario where the model that was a job property is deleted as part of that job. So when the listener is deserializing the job payload, the model can no longer be reconstituted and the exception is triggered.