When a recipe does not run, the cause is almost always one of a handful of things: a switch that is off, a run limit that was reached, a trigger that fired before the recipe was ready, or a redirect in a place it cannot work. This article is the checklist our support team runs through first, followed by where the status and tools pages went in Uncanny Automator 8.0, the considerations that matter as your recipes grow, and how to reach us.
Check these first
- The recipe and every item in it are switched on. A recipe saves automatically while you build it, but it runs only while Recipe on is switched on in the top bar of the recipe builder. Each trigger and action also has its own On / Off switch on its node, and an item that is Off does nothing. The most common reason a new recipe “doesn’t work” is that it was built and never switched on.
- Times per user has not been reached. Times per user, in the Settings panel of the builder sidebar, caps how many times one user can complete the recipe. A new recipe shows Unlimited here; if you set it to 1 for a recipe that should happen once for each user, your second test as the same user does nothing, and no new entry appears in the logs. While you are testing, set it to unlimited, then put the limit back. See Recipe settings: times per user, total times and throttling.
- The event happened after the recipe was on. Automator starts watching for a trigger’s event only once the recipe is on. It cannot react to anything that happened earlier. If the trigger is a product purchase and a user bought the product last week, switching the recipe on today does not run it for that purchase, only for purchases from now on.
- Every trigger has completed, if the logic is All. A recipe with more than one trigger shows a sentence above the Triggers section, Run recipe when Any of the triggers is completed or All of the triggers are completed, and you switch between them with Change trigger logic. With All, the actions wait until the same user has completed every trigger, each of them after the recipe was switched on. With Any, one trigger is enough. If a recipe with two triggers seems to ignore the first one, check which logic it uses. See Managing triggers.
- A redirect has a browser to redirect. The Redirect to a URL action sends the visitor to another page, so it works only when the trigger happens during a normal page request by that visitor. It cannot fire from a Queue block, inside a Loop block, or from a background run. Events that complete with JavaScript rather than a page load, such as a LearnDash quiz completion, have historically not been able to redirect either. If several recipes fire on the same event and more than one redirects, the visitor follows whichever ran first, so keep redirects to one recipe per trigger. See Working with redirects.
- Tokens that come back empty may need a moment. Some plugins, LearnDash among them, finish writing the data behind their tokens a fraction of a second after Automator sees the trigger complete. If a token is empty in your email or webhook but you know the value exists, put the action inside a Queue block with the wait mode Set time and a short wait, such as 10 seconds (Seconds is the smallest unit). The actions inside run after the wait, by which time the plugin has caught up, and the rest of the recipe continues without pausing. Recipe blocks require Uncanny Automator Pro. See Queue block: delaying and scheduling actions.
- Read the logs. Every run is recorded. Open Automator > Logs, or click View logs in the Details panel of the builder sidebar to see only this recipe. The Recipe, Trigger, and Action tabs show whether each step completed, was skipped, or failed, and the reason, which usually points straight at one of the items above. A trigger that fires after the recipe has reached its Times per user or Total times limit is not recorded at all, so a missing entry is itself a clue.
Note: When the builder shows a validation message on an item, the Fix with Uncanny Agent button below it asks Uncanny Agent, the AI assistant built into Uncanny Automator, to correct the item for you. It appears only on sites where Uncanny Agent is available, and not when both Uncanny Agent launchers are switched off in its settings.
Where Status and Tools went
Earlier versions listed a Status (or Tools) page in the Automator menu. In 8.0 it is no longer in the menu. Go to Automator > Dashboard and click View full status on the Status card. The page has three tabs:
- Status — the system report: WordPress and server details, plugin versions, the Automator App Platform connection, the database tables, and the active plugins. Click Get system report to copy it all, and paste it into your support ticket. It saves a round of questions.
- Tools — Repair Automator tables recreates any Automator database table that is missing, which fixes the rare installation where a table was not created. Reset Automator log tables deletes every log record and resets every user’s run counts; recipes are untouched, but the reset cannot be undone. Resend App actions re-sends app-integration actions that failed.
- Debug — the debug log settings, for when support asks you to turn logging on.
The page is described in full in Setup wizard and dashboard.
As your recipes grow
Two things catch people out once recipes are in daily use.
Deactivating a plugin that a recipe uses. A trigger belongs to the plugin whose event it watches. If that plugin is deactivated, the trigger can never complete, so the recipe stops running until you reactivate the plugin or delete the trigger. An action from a deactivated plugin does not run: the run is recorded as Completed with errors, and there is no way to run that action later for the users it missed. For example, a recipe with two triggers (a form submission and a WooCommerce purchase) and two actions (enroll in a LearnDash course and send an email): deactivate LearnDash and users receive the email but are never enrolled; deactivate WooCommerce and the recipe never runs, because the purchase cannot happen. Before deactivating a plugin, check Automator > Recipes for recipes that use it.
Email actions that fire often. If a recipe sends many similar emails in a short time, the delivery service decides what arrives. Third-party services such as SendGrid, SparkPost, Amazon SES, and Gmail may drop identical messages sent in succession or limit how many you can send per minute. If notifications go missing under load, check the sending service’s logs before the recipe’s.
Getting help
If the checklist does not explain what you are seeing, it is fine to ask. Open a ticket at automatorplugin.com/automator-support/ and include the system report from View full status, the name of the recipe, and what you expected to happen. For an error message inside the recipe builder itself, follow Troubleshooting plugin errors first; it walks through finding a plugin or theme conflict.
Related: Creating a recipe, Recipe settings: times per user, total times and throttling, Managing triggers, Working with redirects, Troubleshooting plugin errors
Comments (0)