Kai Schlamp

Hi @ashleyheath. We completely refactored the worker for the upcoming v3 release (done mainly by @onlyann). Would you mind looking [at the new implementation of the worker](https://github.com/procrastinate-org/procrastinate/blob/v3/procrastinate/worker.py). Do you think...

What version of Procrastinate are you using? Have you recently upgraded? > ``` > db | 2024-07-10 18:00:36.635 UTC [39] ERROR: column "priority" does not exist at character 31 >...

Maybe we should also add a more obvious hint on the documentation's start page or the quickstart page that a manual migration step may be required after a package upgrade...

Have you tried upgrading the package and applying the migrations? Does the problem still exist? What's the retry strategy? How does the task look like?

I wouldn't call it minor. It's something that should not happen. From looking at the worker code, the [retry happens before the status of the job is changed and the...

As cool as something like Mermaid is, our state chart isn't that difficult (and hopefully consistent as soon as we get the "aborting" state caused by me out again 😞)....

I also gave it a shot using Mermaid but in raw mode, and I think it's quite pretty 🙂. I used the "neutral" theme, which looks ok in light and...

Closed by #1208

@ewjoachim, is there anything we still have to do here?

In Django, database connections are typically managed through the request/response cycle of a view. However, in background jobs, there is no request/response cycle, which means these connections won't get closed...