Integrations going to 500 Error in Kuali Platform (US region only)

A routine security upgrade to a third-party networking library changed how outbound secure connections were handled, causing integrations in our US regions to fail from approximately **September 5 at 7:43 PM MDT through September 7 at 6:41 AM MDT**, Canada was not affected.

### Resolution and Follow-Up

We rolled back the upgrade and retried affected documents. We have also added automated testing and are improving monitoring and alerting to help prevent and more quickly identify similar issues in the future.

From approximately Sat Sep 5, 7:43 PM MDT to Mon Sep 7, 6:41 AM MDT, integrations in our US regions were failing with status 500 errors. We've corrected the issue and scripted a retry on all affected documents.

This was caused by a routine security upgrade to a third-party networking library, which changed how outbound secure connections are made and prevented integration requests from reaching their destination. No data was transmitted to external systems — affected steps simply did not run.

We've rolled back the upgrade and added automated test coverage for this path to prevent a recurrence. Our Canada region was not affected.