iPipeline incident

iGO- Guardian - some eApps are failing to process on the client’s system due to a missing agency code – PROD

Minor Resolved View vendor source →

iPipeline experienced a minor incident on August 14, 2025 affecting iGO, lasting 21m. The incident has been resolved; the full update timeline is below.

Started
Aug 14, 2025, 08:04 PM UTC
Resolved
Aug 14, 2025, 08:26 PM UTC
Duration
21m
Detected by Pingoru
Aug 14, 2025, 08:04 PM UTC

Affected components

iGO

Update timeline

  1. identified Aug 14, 2025, 08:04 PM UTC

    On August 12, Guardian reported eapp processing issues affecting certain cases. This was traced to a recent project release on August 9, where a scenario requiring an agency code was missing, causing the application to fail to process in the client’s backend system. The team has identified the fix, which is scheduled for release on Saturday, August 16. In the meantime, the Support team is manually correcting affected cases as they are identified. -- iPipeline Support

  2. resolved Aug 14, 2025, 08:26 PM UTC

    The earlier communication was sent in error and should be disregarded. Please ignore the message, and we apologize for any inconvenience caused. -- iPipeline Support