Failures with McLeod-integrated TMS configurations

We're continuing to work with McLeod to fully resolve the issues impacting our mutual brokers. For some brokers, McLeod has already staged the code fix that can be deployed by performing a Production Application Server Restart. Before performing the restart, it is important that you verify the status of your code fix. You can do this by reaching out to your McLeod Account Representative directly or checking for any notifications from McLeod related to recent releases. Until the code is staged and the restart takes place both real time monitoring alerts from Highway and inbound load lock data to Highway could be impacted.

We are continuing to work with McLeod's engineering team to implement the acceptance of `bigint` instead of `int` values for the Event ID field in each carrier alert being sent from Highway to McLeod. We appreciate your patience.

Our teams have confirmed that all TAI-integrated configurations are functioning as normal. We are observing similar behavior with McLeod-integrated configurations and are working with McLeod's engineering team to enable `bigint` values instead of `int` for the same affected data field. Please continue reaching out to our Solutions Engineering team with any questions.

The health of all TAI integrations has been restored and failed alerts have been successfully resent. We are continuing to work with proprietary TMS webhook integrations. Please continue to reach out to our Solutions Engineering team with any questions.

We are currently observing failures with TAI-integrated and webhook-integrated TMS configurations. These failures are stemming from a change in the size of the Event ID field in each carrier alert being sent from Highway to affected TMS integrations.

Immediate developer action is required to update the underlying validation on this field and begin accepting `bigint` values instead of `int` for this field specifically. Once this has been updated, the Highway team can re-send any resulting failures. Please reach out to our Solutions Engineering team with any questions.