Incoming customs messages not being processed

Resolved
Resolved

All new incoming customs messages are being received and processed correctly. Messages that were received earlier (including DMS and EMCS messages) have been successfully restarted and processed.

If you believe any messages are still missing, please contact Support for assistance.

Root cause: The issue was caused by an authentication problem between Datahub and Business Central following a recent change by Microsoft.

Resolution & mitigation: Authentication has been restored and the affected flows have been restarted. To prevent similar issues in the future, monitoring and alerts have been implemented to detect and address this situation at an early stage.

Updated

New incoming customs messages are now being received and processed correctly.

Recovery actions are still in progress regarding for customs messages that were received earlier. To prevent duplicate processing, we kindly ask customers not to restart any flows at this time, as this is being handled by our teams.

We will provide a further update once recovery is complete.

Recovering

The underlying issue has been resolved. Incoming customs messages are starting to process again, and we are closely monitoring the system to ensure full recovery.

Investigating

We are aware of an issue where incoming customs messages are currently not being processed. Our teams are actively investigating the cause and working to restore normal processing as soon as possible.

We will provide an update once more information is available.

Began at:

Affected components
  • Integrations
    • Customs