Repository navigation
Replies: 1 comment
|
Thanks for reporting this. I checked current source too: the middleware supports a release delay, but the root and child workflow middleware pass I have accepted the configurable delay as a product improvement and opened #897 with the implementation and real queue-contention acceptance criteria. It will preserve existing behavior by default, cover child inheritance and continue-as-new, and document the effect of Laravel queue attempt limits. The current-source fix needs to qualify before deciding a separately scoped 1.x backport. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
At least on version 1.0.69 there isn't a option for setting WithoutOverlappingMiddleware
releaseFortime, so all messages are immediately visible on the queue when they hit the lock. There could be a option on WorkflowOptions for setting the lock release timeout.All reactions