Flow
The Flow page acts as a central control panel for all Robility Flow schedulers within a project. It provides a unified view where users can monitor, manage, and analyze workflow executions that are triggered either by time or by queue events.
1. Time-Based Scheduler
The Time-Based Scheduler is used to execute workflows at a predefined time or on a recurring schedule. It supports automation for workflows that need to run daily, weekly, monthly, or at fixed intervals.
Scheduler Details
a. Scheduler Name: Displays the name assigned to the scheduler.
b. Scheduler Type: Indicates the type of scheduler (e.g., time-based).
c. Workflow Name: Shows the workflow linked to the scheduler.
d. Version: Displays the version of the workflow being executed.
e. Status: Indicates the current state of the scheduler (e.g., Idle, To Check, Running).
e. Start Time: Shows when the scheduler is set to begin execution.
f. End Time: Shows when the scheduler is set to stop execution.
g. Execution Count: Displays the total number of workflow executions.
h. Trigger Count: Shows how many times the scheduler has triggered the workflow.
i. History: Provides a record of past executions, including status and runtime details.
j. Click View to see the overall execution history.
k. Each row can be expanded via View to access detailed execution logs.
2. Queue-Based Scheduler
The Queue-Based Scheduler triggers workflows based on items available in a selected queue. It enables event-driven automation, making it suitable for processes that depend on incoming transactions or queued data.
Scheduler Details
a. Queue Name: Displays the name of the queue linked to the scheduler.
b. Workflow Name: Shows the workflow executed for the queue.
c. Version: Indicates the version of the workflow being used.
d. Status: Shows the current state of the scheduler.
e. Last Start Time: Displays the most recent workflow start time.
f. Last End Time: Displays the most recent workflow completion time.
g. History: Provides a record of previous executions, including status and timing details.
h. Click View to explore detailed execution information.
Stop Running Flow Executions
The Stop functionality allows you to initiate a stop request for a running Robility Flow from the Automation Ops page. It supports flows triggered by both time-based and queue-based schedulers.
When you initiate a stop request from Manager, the flow stops when it reaches the next Stop Workflow component. If the workflow does not contain this component, the request can still be initiated, but the flow continues executing until completion and then moves to the Idle state.
Prerequisites
Before initiating a stop request, ensure that:
1. The Robility Flow execution is in the Running state.
2. You have access to the Automation Ops page.
For the flow to stop through this mechanism, the workflow must contain a Stop Workflow component.
Stop a Running Flow
Follow these steps to initiate a stop request for a running Robility Flow execution:
1. Navigate to the Automation Ops page.
2. Open the Flow tab to view flow executions.
3. Locate the flow execution that you want to stop.
4. Verify that the execution is in the Running state.
5. Click Stop for the selected execution to initiate the stop request.
6. Monitor the execution status on the Automation Ops page.
7. Verify that the status changes to Stopped after the flow has actually stopped.
The Stop action applies only to the selected flow execution. Other running executions remain unaffected.
How the Stop Functionality Works
After you initiate a stop request from Manager, the flow processes the request when it reaches the next Stop Workflow component.
a. When the flow reaches a Stop Workflow component: The flow stops when it reaches the next Stop Workflow component after the request is initiated.
b. When the flow has already passed a Stop Workflow component: The flow continues executing. If another Stop Workflow component exists later in the workflow, the flow stops when it reaches that component.
c. When the workflow does not contain a Stop Workflow component: A stop request can be initiated from Manager, but the flow continues until execution is complete. It then transitions to Idle if the execution succeeds or To Check if further review is required. The execution status does not change to Stopped, as this status is displayed only when a Stop Workflow component halts the flow.
d. When the flow has stopped: Manager updates the execution status to Stopped only after the flow has actually stopped.
This behavior applies to both time-based and queue-based scheduler executions.
Understand the Stop Status Lifecycle
The execution status indicates the progress of the stop request.
Stop Request Status
| Status | Description |
|---|---|
| Stop Initiated | The system initiates the stop request before calling the Stop API. |
| Stop Accepted | The Stop API has accepted the stop request for processing. |
| Stopped | The system has received confirmation that the flow execution has stopped. |
- Stop Initiated and Stop Accepted do not mean that the flow has already stopped.
- The status changes to Stopped only after the flow has actually stopped.
- Once the status changes to Stop Initiated, another Stop request cannot be submitted for the same execution while the existing request is being processed.
Troubleshooting
| Issue | Recommended Action |
|---|---|
| The Stop action is unavailable. | Verify that the flow execution is in the Running state. |
| The flow continues running after the stop request is initiated. | Check whether the flow has reached the next Stop Workflow component. If it has already passed a component, verify whether another component exists later in the workflow. |
| The workflow does not contain a Stop Workflow component. | Add the component at the appropriate point in the workflow if you want the flow to stop through this mechanism. Without it, the flow continues executing until completion and then moves to the Idle state. |
| The stop request fails. | Review the displayed error message, resolve the reported issue, and retry if appropriate. |
| The execution status does not update. | Refresh the Automation Ops page and check the latest status. If the issue persists, contact the support team. |
| The execution is already stopping. | Check the current status. Another Stop request cannot be submitted for the same execution while the existing request is being processed. |
