Table of Content
Still need help?
Request support
Request Support

Workflow Logs

This article explains the execution of the workflows that are shown as workflow logs.


All the workflow steps and statuses are recorded as workflow logs when a workflow is executed.


Workflow Status

Running - The workflow is being executed and is running

OK - The workflow has been successfully executed.

Error - The workflow has not been successfully executed.


Importance of Workflow Logs

Workflow logs help in determining whether the execution has been successful, failed, or is running.

After the workflow is executed, refresh the workflow logs tab to see the status as OK in a green coloured background or Error in a red coloured background. Admins can click on a log to view a right panel showing details of each node, including successful nodes in green and errors in red, along with the error type.

You can also see the details of each workflow step.

After the workflow is executed, refresh the workflow logs tab and the status will be OK in a green coloured background if successful, ERROR in red, or in case the workflow is still running, it will mention the workflow node in blue.


Use Case

Consider the following workflow:


When a user submits on the app, the workflow starts the execution. The status of Running is shown in a blue coloured background.


Workflow Management Enhancements

Admins can now rerun completed workflows, even after submission edits, and stop currently running workflows directly from the workflow logs tab. This enhanced functionality offers greater control and flexibility in process management.

Rerunning Completed Workflows: App admins have the ability to rerun a completed workflow process. This feature is particularly useful if any changes are made to the submission post-initial execution. By rerunning the workflow, admins can ensure that all updates are processed correctly without needing to manually trigger each step.


Stopping Running Workflows: If there is a need to halt a workflow that is currently running, such as one that includes a wait node scheduled to continue after a certain period, admins can now stop the process mid-execution. This provides the flexibility to manage and control workflows more effectively, preventing unnecessary actions or errors from propagating.



1. The workflow will be logged as running when the execution starts and will be automatically changed to either OK or Error.

2. If the workflow is logged as an error it does not necessarily mean that all the steps in that workflow have failed. If any one of the workflow steps has failed to execute then the overall workflow will be logged as failed.

Try our free plan
It will answer many more questions within just 15 minutes.