How to debug failed integration steps from email data
How to debug failed integration steps from email data
The email notification provides an admin or a tech lead with all the debugging data without the need to log in to the Next Matter app to investigate.The email is enriched with the X-Custom-Data header that you can decode:
- Open the email to view its source. For example:
- In Gmail, click the three dots (⋮) in the top right and select Show original.
- In Outlook Web, click the three dots (⋮) and select View source.
-
Search for X-Custom-Data.
- Copy the data into a base64 decoder. You can use this decoder (external link).
The
status and body information is displayed for custom integration steps, and debug_errors for most of our no-code steps.Workflow stops and shows the 401 error
Workflow stops and shows the 401 error
Check custom integration steps and verify that the phrase Api-Key is present in the Header.
- In the left-hand navigation, click Workflows.
- Click the workflow containing the integration step.
- Click Settings to edit the step.
- Make sure your API key is preceded by the Api-Key phrase.
I'm getting an Unauthorized error when I try to push data to Google Sheets
I'm getting an Unauthorized error when I try to push data to Google Sheets
Why does my integration step show as skipped?
Why does my integration step show as skipped?
This happens if you have selected to skip a failed step. You can configure this in the step’s settings in the On Failure section. Probably the step failed and it was skipped.
<div>.The data reference gets pushed to an external system as raw variables, not the actual data
The data reference gets pushed to an external system as raw variables, not the actual data
This might happen when you edit the Body in an external JSON editor and then copy it over to Next Matter. Data references need to be selected directly in Next Matter (by clicking the braces and selecting the value from the dropdown).
Why is the variable I created breaking my integration?
Why is the variable I created breaking my integration?
It might be because there are brackets or braces to the variable name. Make sure the name doesn’t contain any brackets or braces.
I'm getting a Step not found error
I'm getting a Step not found error
If you’re getting this error when clicking Test integration in the Complete step automatically template, it’s because the auto-complete step relies on the instance ID of the running instance. Clicking Test integration in the editor with no running instance will always produce this error, even if all placeholders are correct.
My instance gets stuck on an integration step
My instance gets stuck on an integration step
If this happens, try refreshing the screen.
How do I retry and update a failed step?
How do I retry and update a failed step?
Your integration test might fail with a Bad gateway or Not authorized error. In such cases, you can take over a step, reconfigure it, and retry.
You can take over a step if you’re a workflow owner or a workflow tech lead.
The condition I created for a form field doesn't work
The condition I created for a form field doesn't work
It might be because you’ve edited the value that’s used in the condition, and you haven’t updated the condition itself.
I'm getting the 429 error
I'm getting the 429 error
This means you’ve hit the rate limit and need to monitor your API usage to stay under the 10,000 requests/hour limit. Instead of skipping the step automatically, select the Allow manual retry option and retry the failed step.
I can't take over an instance
I can't take over an instance
Check that the instance hasn’t been stopped - stopped instances cannot be taken over.
My integration fails with 500 Internal Server Error
My integration fails with 500 Internal Server Error
This indictes issues with the external service that is being called - check the 3rd party endpoint.
Step doesn't automatically start
Step doesn't automatically start
If this happens, check the following:
- Has the previous step completed or is it still in progress?
If the previous step is in progress, the next one won’t start.
A step will not automatically start if all the required fields in the previous step haven’t been filled in. - Is the automation step properly configured? Are there any dependencies and conditions on the step?
- Was the step modified recently?
If the workflow was updated (e.g., new automation logic added) after the instance was already running, the changes might not apply retroactively. - Is the step expected to be triggered is an automation step?
Manual steps must be assigned to someone or explicitly opened. Automation steps that follow manual steps require manual steps to be completed.
Do the following to troubleshoot:
- Preview the instance in the Builder to see the logic flow.
- Check instance logs.
- Retry trigger:
- If it’s a webhook: resend it.
- If it’s conditional: update the input and recheck.
- Manually complete the preceding step.
Read-only table blocks step completion
Read-only table blocks step completion
If a read-only field is marked as required and prefill fails (i.e., table is empty), users cannot complete the step. Try unchecking the Required option for read-only fields unless prefill is guaranteed.
My instance fails without any clear error
My instance fails without any clear error
This usually happens when one of the following is true:
- Rate limit has been exceeded (429 status)
- There are JSON body formatting issues in integration steps (for example, the
//this is a placeholdernotes are left in the JSON) - The required fields are not populated in API calls
When the workflow configuration is correct, retry the instance.
My Apple Script integration fails
My Apple Script integration fails
Retry the step a few times before skipping it.
My routing step fails with a connection error
My routing step fails with a connection error
This might be caused by faulty routing step configuration - verify that the steps have a **Directs to… **option filled in so that it’s clear where each decision should be pointing.