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
Hi,
We are using redbeat in production and manage periodic task dynamically inside tasks. Some of tasks must be send periodically and run one task instance at once. In default, tasks send from redbeat to celery, these are been queued and not applied immediately. This behavior causes some error and manipulated result in our project. We check available solutions to fix our issue and come up with these:
add "max running number" in Entry meta keys and check number of running task in reschedule method
add expires argument in _maybe_due_kwargs and pass argument in "maybe_due" method.
Are these solutions are ok in redbeat?
If its ok, please let me to develop these features in redbeat.
Thanks.
The text was updated successfully, but these errors were encountered:
Hi,
We are using redbeat in production and manage periodic task dynamically inside tasks. Some of tasks must be send periodically and run one task instance at once. In default, tasks send from redbeat to celery, these are been queued and not applied immediately. This behavior causes some error and manipulated result in our project. We check available solutions to fix our issue and come up with these:
Are these solutions are ok in redbeat?
If its ok, please let me to develop these features in redbeat.
Thanks.
The text was updated successfully, but these errors were encountered: