How to find an error – Integry

You can use the 'Integrations View' to debug integrations, check the tasks being consumed by any user or integration, or see if every step of the flow is performing as intended.

Let's say you have been reported an issue with a Mailchimp integration with integration ID: 168379 by a user: zahranaseem(unj3guuhh)-4342

Go to the Flows tab from the top menu. You'll see a list of all your published flows.
- At the top of this page, you'll see the Flow Name, Apps, Integrations, last edited date, and Flow Status. The Status could be Published, Archived or Draft, depending upon the current state of the Flow.
- Click "Published" at the top left to access draft, archived or all flows.
- Search for the Mailchimp flow by its name in the search bar.
- You can also filter a flow based on the apps used inside the flow and its last edited status.
Select the Mailchimp flow.
Click the number under 'Integrations.'
- This is the total number of integrations enabled against the flow you selected.
- You'll be redirected to a page that shows a list of all the integrations created/enabled by your users.
- The details of the columns shown in the table are:
  - Integration ID - The unique ID of an integration assigned by Integry.
  - User ID - This is a unique ID assigned to an end-user by your (or a third-party) app.
  - Date Created - The date and time of an integration created. You can click on the arrows to sort the list of integrations from newest to oldest or vice versa.
  - Last Run Status - This is the status of the last step in the integration. There can be the following states:
    - OK - Integration ran successfully
    - Failed - Failure in a step occurred
    - Running - A run is being executed
    - Hasn't Run - The integration hasn't been initiated yet
  - Integration Status - The current state of an integration:
    - Initializing - The trigger is received and the integration is launching
    - Enabled - A trigger can be received for this integration
    - Disabled - A trigger cannot be received for this integration
    - Blocked - The integration is not active because too many errors have occurred or due to a billing issue
    - Failed to Initialize - The integration could not be launched
    - Deleted - The integration has been deleted. Once deleted, an integration cannot be re-enabled. Therefore, it's advised to disable your users' integrations before permanently deleting them
- Click on the three-dots menu on the far right of the integration to delete, disable an integration. You can also preview integration setup from here.
- You can also filter the list of integrations on the Integration detail page. Before applying a filter, your integrations will be viewed as 10 integrations per page by default.
- You can also click "Filter" on the right to apply filters on the integrations list based on its creation date, last run date, last run status, and integration status. Click "Apply."
Search for problematic integration based on its integration ID or the user ID.
Click "View" to see the run details of the erroneous integration.
You'll be redirected to the Run Detail Page where you can view all the runs executed for an integration.
- At the top, you'll see Flow and integration details and then a list of all the runs executed for this particular integration. For each run, the following information is displayed in the Runs table.
  - Run ID - The unique ID assigned to each run of an integration.
  - Trigger App - The application that initiates the run and launches an integration.
  - Trigger Name - The name of the Trigger configured in the App Connector.
  - Trigger Type - Trigger type configured in the App Connector, e.g., Webhook or poll-based.
  - Start Time - When the run initiates.
  - Duration - The amount of time it takes to complete an execution of a run.
  - Status - This shows if the run executed successfully or not.
  - Network Code - This is the HTTP response status code for the last step of a run, e.g., 200, 404, 500, etc. See a complete list here.
- You can click "Filter" on the right to apply filters on the runs list based on its run date, status, and network error code. Click "Apply."
- You can also search for a run by entering its ID or Trigger App.
- You can also click on the three-dots menu to copy the link of the run and share, retry running it or view GCP error log.
Click on 'View' to see the steps of the flow that failed to execute as intended.
You will be taken to the Step Detail Page where you can find out which step failed for an integration run.
- At the top, you'll find the information about the integration and the run the steps belong to. Then you'll see the following information for the steps of the chosen Run.
  - Step ID - The unique ID of the step.
  - Step App - The app being used in the step.
  - Step Name - The name of the step.
  - Start Time - The time when the step was executed.
  - Duration - The amount of time the step took to execute.
  - Step Status - This indicates whether the step was executed successfully or not.
  - Network Code - The HTTP response status code for the step.
  - View Payload - Click on this button to view the payload of the API Call made at the chosen step.
Click 'View Payload' of the failed step.
You will see the payload view.
- You can choose to view Request, Response, or Object of the payload. By default, the response section is selected because that's how you'll know about the error.
- You can diagnose the error in this section.
- Click on 'View Mailchimp API docs.' This will take you to the API and error documentation of Mailchimp. You can understand the error type and the reason behind the occurrence of an error.
- If you are not able to resolve the error, you can copy the error response from here and share it with our customer support team. We'll resolve it for you.
- You can view the headers and body (raw and parsed) of the API response received for a step from the Response section.
Click on Request to view the request URL, headers, and body of the API request made for a step.
Click on Object to view the key-value pair created by Integry to store the data for the step. For example, an email could be saved as a key-value pair which can later be fetched for different purposes.
Click on Set up notifications at the bottom of the screen to get notified about errors in your users' integrations.
A notification message pops up where you can choose to set up the notifications at the moment or later.
- Click 'Yes' to set up error notifications.
Your account settings screen will open in a new tab in your browser where you can setup or manage your notifications.
The screen is divided into three parts.
- You can select an app to send the error notifications to. When an error occurs in any integrations created from any of your flows, a notifications will be sent to your selected app with a link where you can analyze the failed integration in the Integration View.
- In the second part, you can enter a URL to which the error notifications will be sent. Click Save.
- In the third part, you can mute repeated error notifications for recurring errors and choose to send a single notification after a certain time.
Click 'Manage' to move to the manage section. This is where you will see the integrations you made with your selected apps for receiving error notifications in the Settings section.