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
I just wanted to ask real quick before I dig deeper in to the issue - the cloud tasks generated by this package don't support 'withoutOverlapping' do they? At least it does not seem to work for me.
I kind of need it due to some jobs that should only be maximum of once per cron interval (especially when one job happens to take longer than one cron interval).
I was thinking of creating a cache based boolean lock for the dispatcher, but it seems kind of silly and hacky.
I haven't looked too much into how the ->withoutOverlapping() and existing job detection works right now, so I thought I'd just ask if it's something the developers have already looked into and deemed possible or impossible with cloud tasks. Or maybe the cache based boolean lock really is the way to go?
Thanks!
---- UPDATE
Seems like implementing Laravel's "ShouldBeUnique" interface essentially provides me with the exact same cache based boolean lock I was looking for. Seems like that's the solution for me. Thanks!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey guys!
I just wanted to ask real quick before I dig deeper in to the issue - the cloud tasks generated by this package don't support 'withoutOverlapping' do they? At least it does not seem to work for me.
I kind of need it due to some jobs that should only be maximum of once per cron interval (especially when one job happens to take longer than one cron interval).
I was thinking of creating a cache based boolean lock for the dispatcher, but it seems kind of silly and hacky.
I haven't looked too much into how the ->withoutOverlapping() and existing job detection works right now, so I thought I'd just ask if it's something the developers have already looked into and deemed possible or impossible with cloud tasks. Or maybe the cache based boolean lock really is the way to go?
Thanks!
---- UPDATE
Seems like implementing Laravel's "ShouldBeUnique" interface essentially provides me with the exact same cache based boolean lock I was looking for. Seems like that's the solution for me. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions