For each flow step in Flow Builder, you can enable debugging to track requests and responses between integrator.io and the flow step application. The logs can assist you when troubleshooting by enabling you to view errors that caused a particular record to fail. You can also access information that may help you determine what you need to fix in your flow to avoid errors or optimize your integration's performance. Flow step debug logs are currently available for HTTP connectors (which include REST connectors). This feature was previously released for webhook listener flow steps, but is now available for all flow step types.
NOTE: In previous versions of integrator.io, you could create a fail step to purposely cause the flow to fail at a certain point. You could then review the retry data to find errors in the data being passed at that point of the flow. Flow step debug logs make that process easier by providing all of the information you would otherwise get from creating a fail step with a cleaner user interface.
Start debug
Before you can review the debug logs, you must turn on the debugger for your flow step. Perform the following actions to start collecting debug logs for a flow step.
- Open the flow step you want to debug.
- Click View debug logs in the upper right corner of the flow step.
- Click Start debug to turn on the debugger. Debug logs will be collected for the period of time you choose from the drop-down list. Choose one of the following time increments for debug log collection:
- Next 15 minutes
- Next 30 minutes
- Next 45 minutes
- Next 60 minutes
- Click Apply to confirm your selection.
- Run the flow (or perform the action that triggers the webhook if debugging a webhook listener). Debug logs on this flow step will be captured for the duration of time you chose.
Review debug logs
- Verify that you have started the debugger for the flow step.
- Run the flow (or perform the action that triggers the webhook if debugging a webhook listener) to review the data sent to and received from the platform for that flow step.
- Open the flow step you want to debug.
- Click View debug logs in the upper right corner of the flow step form.
- Click Refresh logs periodically to retrieve the most recently collected debug logs.
- Click the timestamp of the debug log to review all data sent from integrator.io and received from the application for the flow step you are debugging.
Review the request sent from integrator.io
Click HTTP request to review the request sent by integrator.io.
Body: displays the body of the request.
Headers: displays the Headers of the request.
Other: displays the request URL and the method used by the request.
Review the response returned by the application
Click HTTP response to review the response received by the application.
Body: displays the body of the response.
Headers: displays the headers of the response.
Other: displays response URL and the timestamp of when the response was sent.
Filter debug logs
A list of all calls made to and from that flow step displays. You can filter the list by time, method, or response code.
Filter debug logs by time
Time: Click the funnel icon in the Time column to create a filter for your debug list.
You can choose one of the following timespans to filter your debug logs:
- Last 15 minutes
- Last 30 minutes
- Last hour
- Last 4 hours
- Last 24 hours
- Today (since 12:00 AM of current day)
- Yesterday (between 12:00 AM and 11:59 PM of the previous day)
- Custom (Enter or select the timespan by which to filter your debug logs)
Click Apply to filter the list according to your selection.
Click Clear to remove all filter settings.
Click Cancel to exit the filter without saving changes.
Filter debug logs by method
Click the funnel icon in the Method column to filter debug logs by one or more API call methods. You can filter the list by one or more of the following methods:
- GET
- PUT
- POST
- PATCH
- DELETE
Click Apply to filter the list according to your selection.
Click Clear to remove all filter settings.
Click Cancel to exit the filter without saving changes.
Filter debug logs by response code
Click the funnel icon in the Response code column to filter debug logs by one or more response status codes. Check the box next to any of the following status codes to filter the list.
- All codes (default)
- 200 OK
- 201 Created
- 204 No Content
- 304 Not Modified
- 400 Bad Request
- 401 Unauthorized
- 403 Forbidden
- 404 Not Found
- 409 Conflict
- 500 Internal Server Error
- 1xx: Filter the list by any status code returned that begins with the number 1.
- 2xx: Filter the list by any status code returned that begins with the number 2.
- 3xx: Filter the list by any status code returned that begins with the number 3.
- 4xx: Filter the list by any status code returned that begins with the number 4.
- 5xx: Filter the list by any status code returned that begins with the number 5.
Click Apply to filter the list according to your selection.
Click Clear to remove all filter settings.
Click Cancel to exit the filter without saving changes.
See w3.org for a list of standard HTTP response status codes.
Delete debug logs
Click the Action overflow (...) menu, and select Delete log to delete a debug log from the list.
Comments
Please sign in to leave a comment.