Sudden Disappearance of Data in Amplify Admin UI, Despite Accessibility via AppSync and GraphQL

[Its-suLav-D]

Which Specific Feature is your question related to?

Amplify UI

Question

Hey there!

I've run into a bit of a puzzling situation with my project using AWS Amplify's DataStore. Up until recently, everything was cruising along smoothly. I've been using DataStore for all my CRUD operations and subscriptions, and it's been great. But, out of the blue, I've hit a snag: the content that should be visible in the Amplify Admin UI has vanished into thin air.

What's Going On:

Previously, data visibility and management through the Amplify Admin UI were spot on. Now, despite no changes on my end, the data is playing a game of hide and seek – it's nowhere to be seen in the Admin UI.
The twist in the tale is that when I query the same data using GraphQL through AppSync, it's right there, as expected. So, the data is definitely there and intact, it's just the Admin UI that's giving me the silent treatment. Since, I am using DataStore, my I neither fetch nor perform CRUD from my react app anymore.

Steps I've Tried:

Looked for the data in the Amplify Admin UI, particularly in the DataStore models section.
Noticed that it's like a ghost town – no data in sight.
Switched over to querying via AppSync with GraphQL.

What I'm Expecting:

Ideally, the data managed by Amplify DataStore should be consistently visible and accessible both in the Amplify Admin UI and via AppSync/GraphQL queries.

A Bit More Info:

Everything was smooth sailing until this issue popped up. No major changes were made recently that I can think of. It's a bit like someone flipped a switch and the data just disappeared from the Admin UI.

[ykethan]

Hey @Its-suLav-D, on the browser debug console do you observe any errors/network call failures on the Data manager page?

[Its-suLav-D]

@ykethan I do see network status false.

[ykethan]

Hey @Its-suLav-D, do you observe any API calls errors under the network tab? While on the Data manager, could you refresh the page to ensure the GraphQL API calls are logged then inspect the request and response?

[Its-suLav-D]

@ykethan It wasn't showing anything until yesterday. Now, it started working all of a sudden. I haven't changed anything at all. The only thing that I did was re-deploying my backend like three days ago.

[chrislrobert]

I was wrestling with updating my API keys and then slammed into this issue here. I assumed that it was related to my new API keys, but seeing this issue here it might just be a coincidence. Is there a bad version of Amplify Studio that breaks the Data Manager? I already tried to disable and re-enable and that didn't work. Other ideas, other than sit around praying that it magically starts working again like it did for @Its-suLav-D? I am seeing this issue across four environments that span two AWS accounts.

In terms of console messages:

• 1 of these: 44.46b11459.chunk.js:3 [AwsUi] [awsui-select] The selectedId property has been deprecated. Use selectedOption instead.
• 2 of these: 44.46b11459.chunk.js:3 The schema has already been initialized
• A bunch of these: Third-party cookie will be blocked. Learn more in the Issues tab.

[chrislrobert]

This is what fixed my Data Manager, in the end:

1. amplify env checkout BRANCH
2. amplify api gql-compile --force
3. amplify push -y

Presuming it was related to updating the API key, but heavens, this whole Amplify framework seems to behave in a very random way. Hard to know what's going on.

[Milan-Shah]

Please let us know if you see the issue again, happy to dive further as we arent able to reproduce it in our end.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.