Understanding the Behaviour of Queue Workers when Restarted on Deployment in App Platform

App Platform will effectively kill your worker container, and thus any process it is running at the moment of deployment.

So no, the worker will not do a graceful shutdown and finish processing the job.

But you will not need to do the normal queue:restart either, because the deployment creates a brand new container for the worker.

I am currently also looking into these solutions:

• Restarting the jobs that was not finished before the deployment, effectively continuing the job from when it was killed (requires logic in the job to handle it).
• Or have maybe use a PRE job that waits for jobs to be finished, and thus prevent the deployment in middle of a job execution.

My problem is I have some VERY long running (+5 hours) jobs at times, and waiting for them to finish is not a good solution, but I can restart them and have them continue their loop from the point they were stopped.

I have not found a satisfactory solution to this problem yet, in my use case. I hope above can give you some ideas to maybe handle your situation.

[Adding this after some time without an answer.]

Sorry if my question was a little vague, perhaps if we remove the artisan part; what I’m really trying to understand is the nature of the restarting of worker containers when an app is deployed on App Platform.

So my revised question is:

When a deployment takes place on an App Platform app, if the build succeeds and the deployment is successful, what happens to the existing worker containers? Are they shut down and replaced with new containers?

If so, are the worker containers shut down gracefully? What I mean by that is, are they given a chance to finish processing current tasks, or is the plug simply pulled?