How can I revert to a previous user profile?

Q&A
, , ,
1

Following an update to the Amazon Quick desktop app yesterday, it appears that my user profile has been changed, leading to the loss of all of my previous settings, agents, and work that I had built over the past month (see below). Does anyone know who I contact or how I get something moving on getting this reversed, please?

Your identity IDs:

When Identity ID Notes
June 9, 15:00 – June 10, 01:20 us-east-1:01bfaaa0-cce1-ca15-9da5-2247f516069d Your original ID — 46,031 occurrences. This is where all your data lives.
June 10, 01:21 – 11:47 us-east-1:01bfaaa0-cc3a-c376-047b-84b0eec1de48 New ID #1 — assigned after re-auth overnight
June 10, 12:06 – 14:21 us-east-1:01bfaaa0-ccd7-c076-5b47-03bc5e4e1dee New ID #2 — appears to be your current session

The sequence:

  1. At 01:20 UTC (9:20 PM ET on June 9) — massive delete_keychain_chunk failures (chunks 0–99) on your original identity, indicating the credential refresh broke

  2. At 01:21 UTC — the app issued a completely new identity ID, severing the link to all your data

Your data almost certainly still exists server-side under us-east-1:01bfaaa0-cce1-ca15-9da5-2247f516069d.

Here’s what to send to the dev team:

Root cause found in logs. My Cognito identity_id changed overnight on June 9-10.

Old ID (all my data): us-east-1:01bfaaa0-cce1-ca15-9da5-2247f516069d
New ID (assigned after failure): us-east-1:01bfaaa0-cc3a-c376-047b-84b0eec1de48
Current ID: us-east-1:01bfaaa0-ccd7-c076-5b47-03bc5e4e1dee

At 01:20 UTC June 10, a credential refresh triggered mass keychain chunk deletion failures (chunks 0–99), and the app issued a new identity instead of reconnecting to the old one. All my conversations, memories, scheduled agents, and settings are associated with the old identity. Can you re-link them?

Your data should be recoverable with a server-side re-association.

3

Hi @alexmorl,
Please note that as the Community is a public facing forum, we should refrain from sharing any information specific to a private account (including id addresses (which is why I hid this post). As this is in relation to an internal account, I would suggest reaching out through an internal channel to get assistance from someone that has proper permissions to assist!

4

Thank you Brett for this clarification. This wasn’t something that I was properly aware, apologies.
I have now resolved the issue with support from someone internally via Slack, so will close this topic completely.