-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why Why why Index ... does not exist for model OrgChatRoomMessage #2583
Comments
Hey👋 thanks for raising this! I'm going to transfer this over to our API repository for better assistance 🙂 |
Hey @juri-diener, Thanks for raising this issue. Please try the following steps and let me know if it resolves the problem:
|
So I Re-add the index. Did the push, this worked. But when I removed the index and run amplify api gql-compile I get again this error: |
Hey @juri-diener, Did you run |
Yes I did. And I get the same Error. |
Hey @juri-diener, Apologies for delay in response. Are you still experiencing this error? |
Hey 👋 , This issue is being closed due to inactivity. If you are still experiencing the same problem and need further assistance, please feel free to leave a comment. This will enable us to reopen the issue and provide you with the necessary support. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
21.7.3
Amplify CLI Version
11.0.5
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No Changes
Describe the bug
Hello, I had an Index called orgChatRoomMessageByOrgChatRoom. In the developer process I realized I don't need that index on that field but on a different one. I changed it in the schema.graphql and now I get this Error:
🛑 Index orgChatRoomMessageByOrgChatRoom does not exist for model OrgChatRoomMessage
I tried with amplify push --force
But it's not working I can't push anymore.
Why this is the normal developer process that things changing...
Expected behavior
Should work to rename an index name as well delete an Index on a field in schema.graphql without any errors.
Reproduction steps
Create an index on a field
push the changes to the cloud
then rename or remove that index on the field in schema.graphql
Project Identifier
No response
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: