Workflow Logs

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

‍Where to find it?

Once an app is opened, the admin will be able to find workflow logs under the ‘Logs’ tab at the top. By default, workflow logs will open, but if not, select 'Workflow Logs' under 'Logs'.

Working

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

Workflow Status

Running - The workflow is currently executing.

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 or Running in a blue coloured background in case the workflow is still running. 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.

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.

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.

Workflow Error Notifications to App Admins

App Admins will receive email notifications whenever a workflow execution fails or encounters an error, making it easier to identify and resolve workflow issues.

Only App Admins will receive these email notifications. If any user uses the app and a workflow is triggered but encounters an error and does not execute properly, the notification will be sent to the App Admins. If the user who used the app is not an App Admin, they will not receive the notification.

For example, suppose there is an Email workflow that takes the email address from an Email field in the app (referenced using its field variable). If the user forgets to enter an email address in that field or enters an invalid email address, the email will not be sent. In such cases, the workflow error log will be included in the daily email notification sent to the App Admins. They will receive a single email once a day containing all the workflow error logs, rather than a separate email every time a workflow encounters an error.

This keeps your explanation intact, removes only the conversational phrasing, and makes it read naturally as a help guide without changing the meaning or introducing new concepts.

‍

Note

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.