You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
restart the job server while the job is being processed
The dashboard shows a notification that the server stopped resopnding
click the re-enqueue button in the dashboard for that job before the job is re-enqueued by the system itself
Actual result:
After the sliding visibility timeout is exceeded, a second instance of the job starts.
That's because the JobQueue table gets another entry for the job and the legacy one is used as well when the FetchedAt timestamp is outrun by the timeout
Expected result:
A job can not run multiple times concurrently
There is not more than one entry for each job in the JobQueue table, even if the server restarts/crashes etc.
The text was updated successfully, but these errors were encountered:
rklfss
changed the title
Job runs/enqueued multiple times if server stops while job is processing
Job runs/enqueued multiple times if server restarts while job is being processed
Mar 19, 2024
Scenario:
Actual result:
Expected result:
The text was updated successfully, but these errors were encountered: