Feature request · Reliability & bugs · Blocks work
Retry remote schema introspection automatically on failure
1 source thread · first seen 2022-04
Summary
If a remote schema server is not up when metadata is applied, Hasura starts with an inconsistency that must be fixed manually in the console.
- Affects
- teams deploying metadata and services together in CI/CD
- Workaround
- Manually reload the remote schema, or run external health checks that trigger a metadata reload
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“When remote schema introspection fails, hasura should periodically retry”