m3terDocumentation

On this page

Reviewing and Resolving Integration Events

Five system Events are generated for errors that might occur with your integrations:

  • integration.validation.error

  • integration.missingaccountmapping.error

  • integration.authentication.error

  • integration.perform.error

  • integration.disabled.error

In the Integrations section of the Console on the Integration Events page, you can review and follow up on these integrations error Events to troubleshoot and resolve them. When you have followed-up on an error Event and resolved it, you can select mark it as actioned and remove it from the Events list:

Reviewing and Resolving Events

To review and resolve integration error Events:

1. Select Integrations>Integration Events. The Integration Events page opens and list any existing error Events that have occurred for your integrations:

In this example:

  • An integration.authentication.error Event is listed for a Chargebee integration.

  • Two integration.perform.errors are listed for a Notification integration.

You can read off the details of the Event:

  • NAME. The Event type.

  • DATE. A timestamp of when the Event occurred.

  • MESSAGE. Details of the cause of the Event and suggested remedial action you can take.

  • ACTIONED/NOT ACTIONED. All of the Events are shown as NOT ACTIONED.

Depending on the type of error Event, an appropriate button is also provided and which allows you to follow-up and resolve the error.

2. If you want to follow-up and resolve the error, click the follow-up and resolve button:

  • integration.validation.error. Select View run:

  • integration.missingaccountmapping.error. Select Add Mapping:

    • The External Mappings>Create page opens. The m3ter entity and m3ter entity type fields are automatically populated and you can proceed to create the required mapping. For more details, see Creating and Managing External Mappings.

  • integration.authentication.error. Select Configure Authorization:

    • The relevant Integration Configuration Details page opens and you can proceed to configure the correct authentication for the integration's connection to the 3rd-party system. For more details, see the relevant Integrations topic in this section.

  • integration.perform.error. Select View Run:

  • integration.disabled.error. Select Re-enable:

    • The relevant Integration Configuration Details page opens where you can select to Re-enable the Integration. Note that an integration is automatically disabled if there have been 10 successive previous error Event responses to earlier attempts to run the integration. Please check the earlier error Events to resolve any issues preventing the integration from running before you re-enable the integration.

Marking Events as Actioned

When you have followed-up and resolved an error Event, you can mark it as actioned to remove it from the Events list

To mark an Event as actioned and remove it from the Events list:

1. Select the checkbox of the Event you want to mark as actioned.

2. Select the Mark as actioned button. A confirmation popup appears.

3. Select Yes to confirm. The page refreshes and the checked Event is removed from the Events list.

Tip: Mark multiple Events as actioned? You can check-off multiple Events to mark them all as actioned at the same time.

4. If you want to check again on Events that you've already actioned, enable the Include actioned events? switch. The page refreshes and any actioned Events are added back into the Events list, and are clearly marked as ACTIONED:

Next: Creating and Managing External Mappings


Additional Support

Login to the Support portal for additional help and to send questions to our Support team.