Community
Index flows can use old resource file instead of updated in up to 35 min after it is updated
10 days ago by Dennis
Hi,
- (Red) Sometimes a script have some problems and need to be updated. In this case a problem made it stopped after 55 of 56 states.
- (Blue) I make changes to a script, upload it to git, click synchronize on /admin/resources so Onify gets it and manually run the flow that calls the script from /admin/configuration/workflows, and see that it works as it is Completed with all 56 states.
- (Yellow) The resources for workers are not updated by the synchronize button, but by the sync time in /admin/settings/resources_git_pull_interval. I've set it to 5, which is the smallest possible. This index flow is running every 10 minutes. But even though i updated it at 17:03:00 and manually ran it at 17:03:39, the old script file version was the one used at 17:09:03, 17:18:06 and 17:28:37.
- (Green) Finally, at 17:39:08 the worker is now running the new version! 😍 But this is 35 minutes since I updated it. So you can understand my concern.
Is there some way to not have to wait for the worker like this?
I could think of a few possibilities that would make sense to me:
a) Let the synchronize button at /admin/resources update for not only the api but the worker as well.
b) Add a "flush"-button to each flow in /admin/configuration/workflows. Some type of force sync to update all future processes of the flow to use the new resource.
Kind regards