> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/help-center/help-topics/billing-account/data-payloads-and-destinations/payload-history-ids-after-deauth.md).

# 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.

**Filtering by User or Reference ID only finds connections that exist now.** After a reconnect, the user has a new Terra `user_id` and the old connection is gone, so payloads delivered under the previous `user_id` drop out of filtered results, even when you filter by the same `reference_id`. The deliveries you received are unaffected. Pick up the new ID from the `auth` webhook, and key your own records on `reference_id`, provided you pass the same value when the user reconnects.