GraphQL Schema is not saved after Deployment

[neomhr]

Before opening, please confirm:

• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

App Id

d1fhc0qyyh74sr

Region

us-east-1

Environment name

staging

Figma File Version (if applicable)

No response

Amplify CLI Version

No response

If applicable, what version of Node.js are you using?

No response

What operating system are you using?

No response

Browser type?

No response

Describe the bug

Yesterday, I created a Data Model in the visual editor in Amplify Studio.

After I finished, I saved and deployed my changes by clicking the save and deploy button in the studio.

Now, everything is gone. It did not save any part of my model, even though I followed every step and it even said that deployment was successful. I also checked CloudFormation where I can see a successful deployment yesterday at that time.

Expected behavior

It said the deployment was successful, so I assumed my data model would be saved.

I thought that everything I create in Studio will be actually saved and usable when I click save and deploy. Now it's just completely erased. Luckily I saved the schema locally, but now I have to manually re-do it in studio.

Reproduction steps

1. Build a Data Model in Amplify Studio
2. Click Save and Deploy
3. Log back in the next day and it's completely gone with no way to recover it

Project Identifier

No response

Additional information

No response

[ykethan]

Hey @neomhr, thank you for reaching out. Sorry to hear on the experience.
For a quick check, could you try pulling the application to your local environment and check the amplify/backend/api/<api-name>/schema.graphql file, if the schema file has the data models locally?

We are currently investigating this behaviour and provide an update here as soon we receive any additional information.

[ykethan]

wanted to provide an update, I was unable to reproduce this behaviour. Could you provide us some additional information such as any errors observed in the browser debug console or the Data modelling page and the API configuration?

[neomhr]

for some reason it now worked after re-deploying the data model through amplify studio. I cant reproduce the issue myself now - so guess its fine. thanks for the fast support though!

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