Tirumarai Selvan

@strongSoda Is that all?

That's a good question. One thing you can do is model your application such that an event which updates a resource is only created after the resource is created. You...

Another thing you can do is leverage the idempotency and retry-ability of your functions. This way even if something arrives in a unexpected order, it will fail gracefully and be...

@ameech Yes, few cases can only be solved using a FIFO queue or some well ordered mechanism but do you think this is the common case? Also, it is serverless...

@sebastianbuechler Thanks for reporting. We are looking to revamp the whole app especially to use [Actions](https://hasura.io/docs/1.0/graphql/manual/actions/index.html) as well. We will fix this along-with that.

Great question! I can tell you how you can address this in Hasura GraphQL Engine. With Hasura Event Triggers, what you can do is choose the type of operation (INSERT,...

@bmorelli25 Hey! Do you think this can be merged?

The error `"reason":"Error in $: key \"data\" not found"` indicates that the introspection result (that Hasura performs when adding/reloading remote schema) did not succeed. This typically happens when the remote...

Changing the title to reflect the same.

> We would approach this requirement, by providing a configuration option, say "inconsistentSchemaIsHealthy" (true by default). If this is set to false, then the /healthz will throw 500 in case...