Using Delay Next Step for the flows running in background
We are utilizing the Decisions tool for our client's workflow. Within this tool, we employ the "Delay Next Step" activity. Our functionality includes continuously checking certain database statuses in the background once the flow has started. When all statuses are updated, the flow progresses to the end step.
Comments
-
If a flow is running in the background and the decision server is updated or rebooted, what will happen to the flow? Will the flow automatically restart when the server is back online, or will we need to start the flow again manually?
-
Delay Next Step will not maintain the flow if the server were to go down. If this is something needed, the Pause Flow step is recommended instead.
The Pause Flow step will keep the flow in a Stored Workflow State, which will maintain its process even during a server restart. This step is configured almost identically to Delay Next Step, with the addition of some added options such as the SaveFlowDataOnPause toggle.
Howdy, Stranger!
Categories
- 4.4K All Categories
- 78 General
- 13 Training
- 209 Installation / Setup
- 1.1K Flows
- 110 Rules
- 270 Administration
- 213 Portal
- 497 General Q & A
- 709 Forms
- 345 Reports
- 3 Designer Extensions
- 48 Example Flows
- 58 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 186 Pages
- 5 Process Mining
- New Features
- 186 Datastructures
- 70 Repository
- 229 Integrations
- 29 Multi-Tenant
- 27 SDK
- 81 Modules
- 59 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 143 Lunch And Learn Questions