My workflow isn't running. What do I check?
If your workflow has stopped running or isn't triggering as expected, this article walks you through the most common causes and how to fix each one.
What you might be experiencing
Your workflow is published and active, but data isn't moving between your apps. It may have been running previously and stopped, or it may never have run at all since you published it. You may or may not see an error message in Workflows → Activities.
Possible causes
Work through these in order. The most common causes are listed first.
Task limit reached
Your plan's monthly task allowance has been used up. When tasks run out, Conduitly pauses all workflows automatically until your next billing cycle begins.
How to fix it: Go to Settings → Billing to check your current task usage. You can upgrade your plan immediately to restore workflow runs, enable task overages on your plan, or wait until your billing cycle resets. See Understanding your plan and task limits for more detail.
Workflow is inactive
The workflow may have been deactivated, either manually or automatically after a failed run (if Auto Retry is disabled).
How to fix it: Open the workflow in the builder and click the settings icon in the top toolbar. Check that Workflow Status is set to active. If it's inactive, toggle it on and republish.
App authentication expired or invalid
The authentication for one or more apps in your workflow might be expired or invalid. Some integrations require periodic re-authentication. An API may have expired. Or a user account might have been reset or deactivated. If the connection to a trigger or action app has expired, the workflow will stop running.
How to fix it: Open the workflow, click the affected trigger or action node, and navigate to the Account tab. If the connection has expired, you'll see a prompt to reconnect. Click Connect and complete the authentication flow again. See A connection is broken — how to re-authenticate for a full walkthrough.
Alternatively, check the Accounts tab on the side menu and view your connected accounts for warnings and re-authenticate them.
Workflow hasn't reached its next minimum interval yet
Most workflows check for new trigger events at a regular interval, at minimum every 1, 2, or 10 minutes depending on your plan. If you've just published or recently triggered an event, the workflow may simply not have run yet.
How to fix it: Wait for the next polling interval to pass, then check Workflows → Activities to see if a run has been recorded. If your plan is on the Individual tier (10-minute minimum interval) and you need faster response times, consider upgrading to Pro or Team.
A filter condition is blocking the workflow
If you've set up a filter on your trigger, the workflow will only run when the incoming data meets the condition you defined. If none of your recent trigger events match the filter, your workflow may not have triggered, but the workflow isn't broken.
How to fix it: If you believe that the filter is not being applied correctly, open the trigger or action panel and navigate to the Test tab. Click the filter icon to review your filter conditions. Confirm that your recent trigger data actually meets the conditions you've set, and adjust them if needed.
A trigger or action app is returning an error
If a trigger or action step is returning an error in response to Conduitly, there may be an issue with the 3rd party app the Conduitly integration with them. Sometimes errors may be temporary, such as if an error occurs while an app or Conduitly is conducting scheduled maintenance. Sometimes there may be a deeper issue that requires technical support.
How to fix it: Confirm that the app is not down or undergoing maintenance and that your account is still active. If the app is up and the problem doesn't resolve after retrying, report the issue to Conduitly Support by clicking the ? button at the bottom right of the screen.
An app integration in your workflow requires an update
Occasionally, integrations may be updated by Conduitly due to app API changes, fixes, or improvements. This may require your workflow to be updated with the new integration version in order to continue working.
How to fix it: Edit the workflow. If an integration in your workflow requires an update, a warning message will appear. Open the listed app(s) in the workflow to check for possible new required fields and test the app connection again, then republish the workflow. This will complete the integration upgrade in your workflow.
Still not working?
If none of the above resolves the issue, contact our support team via the Help button in the bottom-right corner of any page. Include the workflow name and a description of the issue you are having. It helps us diagnose the problem faster when you provide clear details.