Is there a way to stop the daily workflow when it runs forever without resetting the DB?
Normally it takes 4 to 6 hours for our daily workflow, but today it has been running for 10 hours, and i cannot import to the db until it finishes. In the past when this has happened i had to reset the DB, but my users are not able to search until the DB re-indexes when i do this, and since i am in the middle of the workday this is not ideal.
Any help?
Robyn
It’s probably not directly related to your question of how to stop the workflow, but it might reduce your need to restart.
- Using Your own Hardware:
We had similar issues of taking too long to run daily workflow or other more processing intensive workflow. So we tested using private server. And the performance improved significantly. With a regular i5 PC that we tested initially, the time required reduced to 30~50% of the cloud service. You can get similar gain if you host it on your own cloud services with sufficient hardware allocation.
The added benefit of using private server is that you can terminate and restart the service yourself when it’s necessary.
However, without using your own hardware, then it’s down to the limited processing power allocated on the shared Ragic cloud service.
- Limiting the number of records.
Another way might be looking at what you are updating, and put filtering condition in your workflow or fixed filter on the form you are updating.
Hi Robyn,
This is Kate from Ragic Support. Currently, Ragic does not support the ability to manually stop or reset daily workflows for individual databases. I’ve relayed your request to our development team, and if there’s any update on this feature in the future, we’ll be sure to share it here.
In the meantime, if you notice that a daily workflow is taking unusually long to complete, we suggest first checking whether there have been any recent changes—such as workflow adjustments or the addition of a large number of formulas—that might have impacted performance. If no changes are apparent, please feel free to reach out to us at support@ragic.com with details about the issue, and we’ll look into it from our end.
Regarding the suggestion shared by Jeremy about the on-premises installation: while this setup technically allows for server restarts that could interrupt daily workflows, we generally wouldn’t recommend switching to on-prem solely for this purpose. The on-premise plan requires a minimum of 10 users, selection of at least the Professional plan (Lite and Free plans are not supported), and must be paid annually. More importantly, managing an on-premise environment involves significant internal responsibilities—such as providing your own server hardware, ensuring network and data security, performing regular backups, and handling system maintenance and performance tuning. These requirements often mean higher resource commitments in both cost and IT expertise compared to using our cloud service. That said, on-premise is a good fit for teams with specific policy requirements or the infrastructure to support it.
Hope this helps! Let us know if you have any other questions.
Thanks,
Kate