Wiresk

Wiresk

Troubleshooting Errors in Wiresk

Estimated reading time: 2 min

When a Flow in Wiresk fails, the platform gives you several tools to understand what went wrong and how to fix it. These tools are built into the Flow Builder and are also accessible through the Statistics panel.

When a Method step fails during execution:

  • A red exclamation mark appears directly over the Method icon
  • The Flow will stop at that step
  • You can click on the red exclamation mark to open the error panel, where the issue is explained
  • In the right-hand panel under Run Results, you’ll see:
    • The exact timestamp of the failed run
    • A red status indicator (such as “0”)
    • Log details and API error messages for debugging
Wiresk Flow Builder interface showing a failed Flow run. The Flow includes a Trigger, a "Find Event" step, and a "Create Event" step. A red error icon appears over the "Find Event" step, with an error message on the left panel: “(404): Not Found Details: [notFound] in global.” The Run panel on the right is set to "Run Flow" with empty JSON input. The run result at the bottom shows a red error indicator for the latest run on 8/1/25 at 10:13:19.

In addition, go to the Flow management section. There, you will see a list of all your Flows.
Each Flow shows a Flow Execution summary with the number of successful and failed runs. This helps you spot Flows that may need attention even without opening them.

Wiresk Flow management dashboard displaying a list of recent and all Flows. Each row shows the Flow name, connected apps (e.g., Google Calendar, Google Drive, Google Forms), Flow execution results (successful and failed counts in green and red), activation status toggles, Trigger icons, and options to favorite or delete the Flow. A red box highlights the “Flow execution” column, showing metrics like 43/22, 96/19, and 6/5 for success/failure counts.

At the bottom-left of the Flow Builder, click Statistics to open a detailed dashboard.

  • The History tab shows each execution with:
    • Process ID
    • Start and end times
    • Final status (Success or Failed)

When you click on a recorded execution, a right-side panel appears showing detailed information for that run. This includes:

  • The step-by-step execution trace, with the Method or Trigger that failed highlighted
  • The input data used for that step
  • A traceLog showing the error message if the execution failed (e.g., (404): Not Found Details: [notFound] in global)
  • Copy buttons for both input and traceLog for easy debugging
Wiresk 2025 08 01 at 10.24.51 scaled Troubleshooting Errors in Wiresk
  • The Report tab shows:
    • Aggregated run counts
    • Line graph of execution history
    • Pie chart comparing success vs failure rate
Wiresk Statistics panel displaying the "Report" tab for the Flow "QA event." On the left, a table summarizes Flow execution results by time period, showing the number of successes and failures. On the right, a line chart visualizes total success and failure counts over time, and a pie chart below shows a success rate of 66.15% and failure rate of 33.85%.

This is especially helpful when you’re monitoring repeated failures or trying to identify patterns over time.

Error TypeWhat It MeansHow to Fix It
Authentication ErrorToken expired or Connection lostGo to My Apps and reconnect the app
Missing Field ValueA required field was left empty or not mappedCheck field mapping inside the Method
Invalid FormatData doesn’t match the required formatAdjust format or transform data before mapping
Permission DeniedAccount lacks access to perform the actionUse an account with the proper permissions
No Matching RecordsFilters or query returned nothingRelax your filters or test with known valid data

Use the Run Once button to manually test your Flow. This allows you to:

  • Preview the Trigger data
  • View each Method’s input and output
  • Confirm mapping is correct
  • Detect format or permission issues before going live

If your Flow uses a Scheduled Trigger, you can also switch to the Run Scheduler tab to perform a force run. This executes the scheduler once using live data from the connected app, without waiting for the next scheduled time. It’s useful to:

  • Verify that the recurrence rule is pulling the expected data
  • Check field mapping with real-time input
  • Simulate a real scenario without waiting for the schedule to trigger

Both options give you immediate feedback and help ensure your Flow is correctly set up before activating it.

After a test or failed run:

  • Open the step with the red error icon
  • Review the error message, input data, and API response
  • Look at the Run Result timestamp to find the corresponding log in the Statistics > History tab

This step-by-step visibility helps you trace exactly where and why the Flow failed.

After correcting the issue:

  • Update field mapping, filters, or Connection settings
  • Re-run the Flow using Run Once
  • Watch for a green icon to confirm the step passed

Repeat this process until the Flow runs successfully.

If you’re stuck:

  • Take a screenshot of the error
  • Copy the Process ID and timestamp
  • Note which Method failed and what app was involved

Send this to Wiresk support for help. They can assist with interpreting API errors or confirming platform behavior.

Learn more about Wiresk, explore our user guide.

If you need an integration that you cannot find in Wiresk, you can make a request to our team, and we will try our best to satisfy your needs.