Troubleshooting integration

Prev Next

When running an integration, issues can occur at several moments and places in the integration. This flow is an example of how and where to search for the source of integration issues.

Usually, if issues occur in an integration, you start your investigation at the message. And from there, if required, you can extend your investigation to other parts of the integration, such as the connections (as defined by the applicable message connectors), data queries (as defined by the applicable message documents), and triggers.

If issues occur, and you use:

  • Staging, you usually start your investigation at the staging journal.

  • Web service actions, you usually start you investigation at the web service action history.

  • Data synchronization, you can also investigate the data synchronization log and the outbound queue.

Note

In the flow diagram, click on a shape to navigate to the related information.

If you click a:

  • ‘Troubleshoot …’ shape, the related section in Design > Testing and troubleshooting > Troubleshooting is opened.

  • ‘Monitor …’ shape, the related section in Operation > Monitoring integrations > Monitor integration - Details is opened.

Flow diagram