How to monitor workflow runs

Every time a workflow processes a file, PixelFiddler records it. The execution history gives you a complete log of every run so you can confirm your images are being processed correctly, spot problems early, and re-run anything that failed.

What execution history shows

Think of execution history as a timeline of everything your workflow has done. Each entry represents one file being processed through your workflow. You can see exactly when it ran, how long it took, and whether it finished successfully.

This is especially useful when you first set up a workflow and want to make sure it is picking up the right files and applying the correct operations.

Accessing execution history

There are two ways to get to your execution history.

From the workflow list

1. Go to Workflows in your space
2. Click on the workflow you want to inspect
3. Select the Executions tab

From the workflow editor

If you are already editing a workflow, you can switch to the Executions tab at the top of the editor to see past runs without leaving the page.

Reading the execution list

The execution list shows your workflow runs in reverse chronological order, with the most recent at the top. Each row represents one file that was processed.

For each run, you will see:

• File path — the image or file that was processed
• Timestamp — when the run started
• Status — whether it is pending, running, completed, failed, or cancelled
• Duration — how long the processing took

The list is paginated with 10 entries per page. Use the pagination controls at the bottom to browse through older runs.

Filtering by status

Above the execution list, you will find status filters that let you narrow down what you see. This is helpful when you have hundreds of runs and need to find specific ones.

The available filters are:

• ALL — shows every run regardless of status
• PENDING — runs that are queued and waiting to start
• RUNNING — runs that are currently being processed
• COMPLETED — runs that finished successfully
• FAILED — runs that encountered an error and did not finish
• CANCELLED — runs that were stopped before they could complete

Tip

After enabling a new workflow, check back in a few minutes and filter by FAILED to quickly spot any issues with your setup.

Viewing stage-by-stage details

When you need more detail about a specific run, click on any row to expand it. This reveals a breakdown of every stage (operation) in your workflow and how each one performed.

Each stage shows its own status, so if a run failed, you can see exactly which operation caused the problem. For example, you might see that the resize step completed but the background removal step failed. This tells you where to focus your troubleshooting.

Note

Stages run in the same order they appear in your workflow editor. If an early stage fails, later stages will not run.

Re-running failed executions

If a run failed due to a temporary issue — such as a brief connection problem or a service hiccup — you do not need to set everything up again. Simply find the failed execution in the list and click the Re-run button to process that file again.

This saves you from having to re-upload or manually trigger the entire workflow. The re-run uses the same file and the same workflow configuration.

Manual execution and testing

Before you enable a workflow’s automatic trigger, it is a good idea to test it manually. Running a workflow by hand lets you verify that every operation works correctly on a real file from your library.

How to run a workflow manually

There are two ways to start a manual run:

1. From the workflow editor — switch to the Execute tab, pick a file from your media library, and click Run
2. From the executions page — click the Run Workflow button, then select a file to process

In both cases, you will choose a file from your connected storage. The workflow will process it immediately, and you can watch the result appear in the execution list.

Tip

Manual runs are the safest way to test a new workflow. Try it with a few different images before turning on automatic triggers to make sure everything behaves as expected.

Troubleshooting common failures

When a run fails, the stage-by-stage view usually points you toward the cause. Here are the most common issues and how to fix them.

File not found

The workflow tried to process a file that does not exist at the expected path. This usually means your trigger pattern does not match the actual file location. Double-check the folder path and file name pattern in your trigger settings.

Permission error

PixelFiddler could not access the file in your storage. Verify that your storage connection is still active and that PixelFiddler has the correct permissions to read from (and write to) your storage.

AI operation failed

If your workflow includes an AI-powered operation like background removal or smart tagging, the run may fail if your AI token balance has run out. Check your account’s token usage in your space settings and top up if needed.

Timeout

Very large images or complex workflows with many operations can sometimes exceed the processing time limit. Try these steps:

• Use a smaller or lower-resolution version of the image
• Simplify the workflow by removing unnecessary operations
• Split a complex workflow into two simpler ones

Caution

If the same file fails repeatedly, expand the run to check the stage details before re-running it. Re-running without fixing the underlying issue will produce the same error.

Next steps

Now that you know how to monitor and troubleshoot your workflow runs, explore these related topics:

Create your first workflow

Set up triggers

Browse available operations