Inbound workflow issues with telematics enabled

We've confirmed the affected functionality is now fixed, so we're marking the incident as resolved.

Specifically, this issue caused an internal error when all of the following were true:

1. Sending an inbound message, action, or workflow using a form with `enable_telematics_data`
2. on an account with a telematics integration enabled, but
3. as a mobile app user who does not have the telematics integration configured

Inbound messages and actions that experience an error are retried, subject to device connectivity. Affected workflow actions will be delivered to your messaging service now that the underlying issue is fixed. Affected mobile apps would have reverted to offline workflow during the incident period from 18:30 UTC until 21:39 UTC.

We're continuing to verify that the functionality is working as expected, although monitoring indicates it's functioning normally. We're also working to isolate the specific configurations that were affected so we can share some additional detail about the scope of the failures. At this time, we believe that actions for users with a telematics integration configured at the account level, but disabled at the user level, were affected.

We've rolled back the associated change and have seen the errors related to retrieving telematics info for inbound workflow actions drop to expected levels.

At this time, we believe workflow actions should be functioning normally, but we are doing additional checks to confirm.

We are continuing to work on a fix for this issue.

We've identified a correlated change to an area of code responsible for attaching telematics info to inbound messages. We are rolling back the change.

We've received some reports of issues with inbound workflow messages that have telematics info enabled starting around 18:30 UTC. Our team is investigating these errors to determine the cause. We'll post another update shortly once we have more information.