hasura / hasura/graphql-engine
Event trigger already exists error
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
### Environment
Hasura hosted environment
### What is the current behaviour?
Error received even though I cannot access the created event trigger, I think that it was not actually created and thus not actually working (thankfully!) otherwise webhooks would be firing without being able to edit the trigger...
### What is the expected behaviour?
Be able to create the trigger
### How to reproduce the issue?
1. Try to create a trigger, received a message on the top right that metadata is inconsistent (even though I fixed metadata in another window, so I guess cache was in play?)
2. Clicked the button in the error to fix metadata.
3. Try to create the trigger again, receive error, cant create trigger with this name ever again
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported Hasura hosted-environment reproduction: create an event trigger, resolve the metadata-inconsistent warning, and retry with the same name. Investigate why the first attempt leaves the name unavailable despite the trigger being inaccessible. Done means the trigger can be created successfully after metadata is fixed, without an erroneous “already exists” error.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100