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
When using the SkipIfBatchCancelled middleware together with failed jobs retries, the jobs that previously failed are marked as successful when one job reaches the failed retry threshold.
Steps To Reproduce
Actual:
Batch 10 jobs
Job 3 and 7 fail
Failed jobs are retried up to retry threshold
Job 3 meets threshold first, marks batch as cancelled
Job 7 is skipped, and marked as successful due to SkipIfBatchCancelled middleware
Expected
5. Job 7 had previously failed, so it should not be marked as successful, it should be marked as failed instead.
The text was updated successfully, but these errors were encountered:
Based on the initial PR the current behavior seems expected, as it skipped handling the job without failing it. I believe you can create a new custom middleware to handle your requirements and fail the job.
Thanks for reporting the problem you are encountering, but it looks like this is a question which may be better suited for a support channel. We only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repository you can try one of the following channels:
Laravel Version
10.4
PHP Version
8.1
Database Driver & Version
No response
Description
When using the SkipIfBatchCancelled middleware together with failed jobs retries, the jobs that previously failed are marked as successful when one job reaches the failed retry threshold.
Steps To Reproduce
Actual:
Expected
5. Job 7 had previously failed, so it should not be marked as successful, it should be marked as failed instead.
The text was updated successfully, but these errors were encountered: