Fix presets or workflows that do not run
Find out whether a saved setup is waiting, has no matching files, or contains an invalid step.
Last updated: 2026-09-11
Quick answer
Check the selected preset or workflow, its timing, and the target files. Manually waits for Apply; delayed modes start a countdown. A workflow needs at least two presets, and its individual steps must have valid actions and matching files. Read the result message before assuming that no work occurred.
Identify what is selected
Choose View > Standard and inspect the sidebar and window title. Confirm that the intended preset or workflow is selected, rather than a different Favorite or an empty temporary setup.
For a workflow, open View > Inspector > Workflow to inspect its ordered presets. Selecting an individual step switches the current selection to that preset; select the workflow again before running the whole sequence.
Check execution timing
| Timing | What to check |
|---|---|
| Manually | Click Apply or use Actions > Execute to run. |
| Immediately | Use a supported execution trigger; simply choosing a sidebar row is not the same as running the Favorites command. |
| After 3s / After 10s | Look for the pending countdown. Clicking Apply in a delayed mode also schedules the delay. |
A timing choice is saved with the selected setup. The workflow's timing controls the workflow run; separate preset delays are not pauses inserted between its steps.
For the complete trigger and cancellation rules, see Choose when presets and workflows run.
Check files and action settings
- Make sure files are actually present in the workspace.
- Clear the filename search for a test and select the intended visible files again.
- For a preset, review its Filters conditions.
- Check its Selected Tags and action. Add, remove-selected, and replace actions need at least one selected tag. Remove All Tags does not.
- Use Manually and a disposable sample file to test after correcting the setup.
A preset with an empty tag selection will not add anything. A matching file that already has the requested tags may be processed without a visible change.
Check a workflow's steps
Open Actions > Manage Presets... > Workflows and select the workflow. It must contain at least two presets. Review the numbered order and the settings in every step.
Each preset's conditions determine whether that step affects a file. Tag conditions can depend on the result of earlier steps, so a change of order can alter which later steps match. A file may pass through the run unchanged because no step matches.
Workspace filename search still matters to the workflow's input. Folder and alias collection also need to include the desired items before the steps can affect them. Use Create, edit, and run a workflow for setup and scope instructions.
When it ran at an unexpected moment
Adding files or invoking a Favorites command can trigger an automatic setup. Select Manually to stop a pending countdown before changing the configuration. This cannot reverse work that has already completed.
Review the shortcut shown next to the Favorite; adding or removing Favorites can change number assignments. Do not assume the same number still points to the same saved item.
When a run reports skipped files or an error
Inspect the workspace's Skipped details when they are offered. Check access to the affected files and reconnect volumes before retrying. For interrupted or destructive changes, inspect the current file tags first rather than assuming the result was rolled back.
If the app is asking for a purchase instead of executing, use Restore purchases and resolve access issues. For a valid setup that still fails, send support the step order, each action and filter, and the exact result message.