Why My Workflow Never Triggers?
This article outlines a step-by-step guide to diagnosing and resolving issues where a workflow is not triggering as expected in the Workflows Module. This checklist ensures the most common configuration issues are identified and addressed.
Introduction
Perspio Workflows allow automation based on asset conditions, telemetry, schedules, or specific events. If a workflow is not triggering as expected, it is usually due to a misconfiguration in one or more of the key components of the workflow setup.
This guide provides a structured troubleshooting path.
Step-by-Step Troubleshooting
1. Workflow is Enabled
Ensure the workflow is enabled.
-
Navigate to Workflows.
-
Confirm the green "Enabled" status tag is present on the workflow tile or in the header of the workflow editor.
If disabled, click Edit, toggle to enable, then click Save.
2. Workflow Type is Appropriate
Check that the workflow type matches the intended use:
-
Continuous: Always running, responds to changes in data.
-
Event: Triggers once per asset when a new event occurs.
-
Periodic: Runs on interval-based triggers.
-
Scheduled: Runs based on time.
-
Suppression: Used to delay or block other workflows.
Navigate to View Options > Group Workflows By > Type to confirm.
3. Condition Group Is Valid
From the workflow editor, click Condition in the sidebar:
-
Ensure all fields are populated correctly (e.g., asset tag, sensor value, operator, and threshold).
-
Make sure the conditions can realistically be met.
-
Avoid conflicting rules (e.g., “temperature > 5” AND “temperature < 4”).
Use the Debug tab to test sample assets against the condition logic.
4. Asset Is in the Right Group
In the Condition section:
-
Confirm asset filter (Tags, Type, Group) matches your intended assets.
-
Use Live Search or Asset Inspector to confirm asset properties align.
5. Schedule Is Running (for Scheduled Workflows)
Go to the Schedule tab:
-
Confirm time, recurrence, and timezone are configured.
-
Ensure the next run time is expected and not in the past.
6. Telemetry Exists for Triggering
Ensure the telemetry or event that should trigger the workflow is arriving:
-
Use Asset Inspector to confirm data points.
-
For Continuous workflows, recent data should be present within the polling period.
7. Actions Are Configured
Even if the trigger works, no action will occur if outcomes are not set:
-
Go to Actions (Trigger) tab.
-
Confirm at least one action is listed (Email, SMS, etc.).
-
Up to 3 outcomes can be selected.
Use Variable Inspector to verify data sources are available for email/phone fields.
8. Suppression Workflow Is Not Blocking
If using a Suppression type workflow:
-
Check the suppression duration.
-
Confirm another workflow hasn’t suppressed execution.
9. Check Audit Logs
Open Audit Logs tab:
-
View recent workflow executions.
-
Identify skipped runs, errors, or asset mismatches.
10. Use Debug Tool
Use the Debug tab in the workflow editor:
-
Select an asset and run a debug pass.
-
Perspio will simulate the condition and return a result.
Useful to confirm if workflow logic is being satisfied.
Conclusion
If your workflow still doesn’t trigger after running through the checklist, it’s likely a logic or telemetry issue. Use Debug and Audit Logs as your final validation tools. For more complex issues, contact Inauro Support for a workflow review.