Skip to main content
Error Logs are available in the settings menu of most workflow types and provide quick access to:
  • Review of any errors that occurred via external calls within the chosen timeframe (24 hours, 7 days, 30 days, or all available)
  • How many times the error occurred
  • The statement that triggered the error(s)
  • The ability to ignore future occurrences of the error, or mark it as fixed

​
Accessing Error Logs

1

Open the Error Logs panel

Click on the icon in the top right corner and choose Error Logserror-logs-20260410-125908
2

Filter and select an error to review

Use the options at the top to filter by time range or refresh if you’re waiting for a specific error to appear, then select the error you’d like to explore further from the list below.error-logs-20260410-125750
3

Review the error information

Error codeThe standardized error message that identifies the error type.Error messageSome errors, such as those triggered by preconditions, can have custom messages attached, which will appear here.StatementThe statement that triggered the error.OccurrencesThe number of times the error occurred.First seenHow long ago the first occurrence happened.Last seenHow long since the most recent error of this type was logged.Error graphShows a graph view of the errors per hour.The error log also provides several actions you can take to manage errors:Ignore this errorMarks the error as ignored, which will cause it to be hidden by default and not appear in the New error count.Mark as fixedMarks the error as fixed. Any reappearances of this error will be flagged as a regression.Captured ErrorsProvides quick access to specific requests from the request history that showcase the error. You can review variable state, inputs, and outputs from here.
Click the next to the Request Input to quickly copy the data sent and run it again using the debugger for further troubleshooting.

error-logs-20260410-130629

​
What’s next

Now that you’re familiar with error logs, head to the Dashboard and review other errors that may be present in your request history. You may also find it helpful to use the Statement Explorer to review other statements of the same type, even if they aren’t experiencing errors currently, to proactively prevent similar issues from occurring.