AX4 incident

Europe Final Instance - EDI Processing Delay

Major Resolved View vendor source →

AX4 experienced a major incident on January 16, 2023 affecting EDI Processing, lasting 6h 46m. The incident has been resolved; the full update timeline is below.

Started
Jan 16, 2023, 09:32 AM UTC
Resolved
Jan 16, 2023, 04:19 PM UTC
Duration
6h 46m
Detected by Pingoru
Jan 16, 2023, 09:32 AM UTC

Affected components

EDI Processing

Update timeline

  1. investigating Jan 16, 2023, 09:32 AM UTC

    Currently, there are performance losses in AX4 regarding the EDI processing. We are working with the highest priority on a solution and will keep you informed.

  2. investigating Jan 16, 2023, 10:11 AM UTC

    UPDATE. Currently, the EDI system has an outage - We are working with the highest priority on a solution and will keep you informed. WEB application is working properly.

  3. identified Jan 16, 2023, 11:13 AM UTC

    UPDATE: EDI System is available again but there are performance losses in AX4 regarding the EDI processing. We are working with the highest priority on a solution and will keep you informed.

  4. identified Jan 16, 2023, 11:26 AM UTC

    UPDATE: We expect that EDI delay will be gone in approx 40 minutes from now.

  5. identified Jan 16, 2023, 12:32 PM UTC

    Update: EDI system is successively processing delayed EDI messages. EDI delay should be gone in around 1 hour from now on.

  6. identified Jan 16, 2023, 01:53 PM UTC

    UPDATE: We need to extend the timeline until the EDI backlog is expected to be gone. We assume that we need additional 50 minutes from now on.

  7. identified Jan 16, 2023, 03:14 PM UTC

    Update: EDI backlog is almost gone. There are only a few messages which are needed to be processed - expected end around 20 minutes. Overall performance of the EDI system is back to normal - we are processing new files within normal velocity.

  8. monitoring Jan 16, 2023, 03:24 PM UTC

    EDI performance is back to normal - EDI backlog is gone. We are now monitoring our system.

  9. resolved Jan 16, 2023, 04:19 PM UTC

    This incident has been resolved.