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
If connection argument is not passed to worker command, failed job insert to separate table is failing, because by generated entities connection field cannot be null.
I think this case it's logic to use default connection name.
Worst thing of this is that failed job is lost - job delete from regular jobs table is in a different transaction an run first. So it's deleted, another transaction with insert fails and it's lost.
Also after this error worker is running, but I think entity manager is closed and worker do nothing, because doesn't get any jobs from database.
The text was updated successfully, but these errors were encountered:
If connection argument is not passed to worker command, failed job insert to separate table is failing, because by generated entities connection field cannot be null.
I think this case it's logic to use default connection name.
Worst thing of this is that failed job is lost - job delete from regular jobs table is in a different transaction an run first. So it's deleted, another transaction with insert fails and it's lost.
Also after this error worker is running, but I think entity manager is closed and worker do nothing, because doesn't get any jobs from database.
The text was updated successfully, but these errors were encountered: