New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delay in date-related Workflows #3246
Comments
Your processes list looks fine. |
We've just double checked - the workflow was triggered after 1 hour and 5 minutes. |
Where do the 5 minutes come from? Isn´t the cron run every minute, so the workflow should work every minute? Also might the --timeout=1800 in our process keep it from working continuously? |
No, this parameter has another function. Date-related conditions are checked once an hour, so for different conversation this delay may be different. You can set custom check interval via But don't make date-related workflows to run very often as it may overload your FreeScout. Like for example running them every minute is obvious overkill. |
Thanks, that could be it! Adding
|
Try (don't forget double quotes):
|
Thanks, this solved our problem we were trying to fix for weeks now!! It would have been great though if this information was publically available as you told us that we have problems with our background-jobs even though it was only delayed because of this setting (see #3221). With the standard setting every time-related workflow can take up to an hour to be processed after it has met its conditions. This is pretty counter-intuitive, you could mention it in the Workflow-Module information. |
Hi,
because of problems with our background jobs we checked the steps in your wiki.
In the first step, your processes look a little different. Could you take a look and tell us, if something in our processes could be the cause?
Thanks a lot!
PHP version: 8.2.8
FreeScout version: 1.8.8
The text was updated successfully, but these errors were encountered: