To find the step that broke, open the failed execution in your automation platform’s run history, identify the first failed step, and inspect its inputs, outputs, and error details before changing anything. Then test one likely fix and retry deliberately—checking for duplicate side effects before replaying the run.
1. Open the failed execution, not just the workflow
Go to the platform’s run, execution, or workflow history and select the specific run that did not complete as expected. The workflow canvas shows how the automation is configured; the run record shows what happened on that particular attempt.
As an Amazon Associate I earn from qualifying purchases.
First confirm the run is actually a failure. A paused run, intentional stop, handled error, or scheduled retry may have a non-success status without indicating that a step needs repair. For example, Zapier documents statuses including Errored, Safely halted, On hold, Handled error, and Scheduled. Read the platform’s status definition before treating a run as broken.
Free tools Windows power users keep installed
One-click scans. No signup required.
2. Locate the first failed step and capture its context
Open the run’s step-by-step details and find the first step marked as failed or errored. Record its name, the displayed error text, and any timestamp or run identifier. The first failure is usually the most useful place to begin: later steps may simply have been skipped because the workflow could not continue.
#1 Best Overall
In Zapier, the run details and troubleshooting view help identify the errored step. In n8n, use the Executions list to select the relevant execution. In GitHub Actions, open the failed workflow run and inspect its job and step logs. Official guidance: Zapier run statuses, n8n executions, and GitHub Actions debug logging.
3. Inspect the failing step’s inputs and response
For an integration or API action, compare what the step received with what the connected service requires. Check mapped fields, values, formats, and any conditions that determine whether the step runs. If the platform exposes request and response details, inspect them alongside the error rather than relying on the status code alone.
- Inputs: Are required fields present, and do mapped values contain the data and format the destination expects?
- Request details: Where available, check the endpoint, method, parameters, headers, and request body.
- Response details: Read the returned status and error message for clues about validation, permissions, rate limits, or a service problem.
Zapier’s HTTP logs can show status code, error message, endpoint, method, parameters, headers, and request body for many failures. Its documentation notes that logs may be unavailable when a step lacks required information. A missing log does not establish that nothing went wrong, and a status code alone may not distinguish a workflow mistake from a credentials issue or temporary service fault. See Zapier’s troubleshooting guide.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 114. Check the likely cause at the failing boundary
Focus on the handoff between the failed step and the service it calls. Review the step’s required inputs and field mappings, relevant filters or conditions, and the permissions or credentials used for the connection. If the error appears intermittent, compare other runs and check the status pages for both the automation platform and the connected service. Zapier specifically recommends checking those sources when repeated 500 errors occur.
Change one likely cause at a time. That makes it easier to tell whether the correction addressed the failure. If the platform supports testing with prior run data, use it to avoid introducing unrelated changes while diagnosing the step.
5. Use the platform’s debugging and retry options carefully
Available controls differ by platform, and some depend on hosting plan, workflow settings, or retained execution data. Use the option that matches your need: inspect a past run, test a correction, or retry an execution.
| Platform | Where to investigate | Debug or recovery options | Important qualification |
|---|---|---|---|
| Zapier | Zap History or the editor’s run details; open the affected step. | Step troubleshooting details and HTTP logs where available; replay failed runs; Autoreplay for certain temporary issues such as a brief API outage or server timeout. | Run statuses have different meanings, and HTTP logs are not available for every failure. Zapier says, “If a Zap errors repeatedly, it will automatically turn off.” See status definitions and troubleshooting and replay guidance. |
| n8n | Executions list; filter by workflow, status, or start time, then open the failed execution. | Retry with the currently saved workflow or the original workflow using prior execution data. A failed execution can also be loaded into the editor for debugging and rerun with that data. | Editor-based debugging depends on hosting-plan availability; execution availability also depends on workflow settings. See execution documentation and debugging documentation. |
| GitHub Actions | Open the failed workflow run, then inspect the job and step logs. | If ordinary logs do not explain the failure, enable additional debug logging. Step debug and runner diagnostic logging are available on reruns. | Use the logs to narrow down whether the workflow, job, or step failed; more logging may be needed when the normal output is insufficient. See GitHub’s debug logging guidance and workflow run logs. |
6. Retry only after considering side effects
A retry can resolve a transient timeout or brief service outage, but replaying a run may also repeat steps that already succeeded. Before retrying, check whether earlier actions created an external side effect—for example, a record, notification, or other change in a connected service. Do not assume the workflow or destination will automatically prevent duplicates.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →- Make and test the likely correction, preferably against the failed step’s available input data.
- Choose the retry or replay option that matches the version and data you intend to use. In n8n, the documented options distinguish the currently saved workflow from the original workflow and prior execution data.
- After the run, inspect the downstream records or actions to verify that the intended result occurred once and that later steps completed.
Zapier documents replay and Autoreplay for certain temporary issues; n8n documents retrying executions with workflow and prior-data options. Neither option means every workflow is duplicate-safe. See Zapier troubleshooting and n8n execution options.
Best Value
7. If the error returns, gather better evidence
When the same step fails again, avoid repeatedly replaying it without new information. Compare the new error with the earlier run, add the platform’s available diagnostic logging, and consult the documentation or support resources for the connected service. GitHub Actions supports step debug and runner diagnostic logging on reruns; Zapier provides step HTTP logs where available and points users to connected-app documentation and support.
When asking for help, include the error text, platform, affected step, and run identifier. Redact credentials, tokens, and sensitive payload data before sharing logs or screenshots. Debugging depth, retained execution data, permissions, and plan availability vary by platform; consult its current documentation for the options available to your account.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →
