Why doesn't payload history metadata match the payload?

When a connection is deauthenticated and reconnected, the dashboard's Payload History may fall back to showing an internal connection ID instead of the Terra…

When a connection is deauthenticated and reconnected, the dashboard's Payload History may fall back to showing an internal connection ID instead of the Terra user_id and reference_id for payloads tied to the now-removed connection.

• The payload body itself (user_id and reference_id in the JSON) remains correct and accurate as delivered.

• Active connections always display correct IDs, so this only affects historical payloads from removed connections.