hasura / hasura/graphql-engine
Event trigger invocation order
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
Hi everyone,
After I did some tests with Hasura and test EVENTS, I repare that events invocation, when I invoke Webhook (HTTP/S) Handler, it dind't follow a order.
In my table called _'cache'_ I have a incremental field named _'index1'_, and I **_INSERT_** in an incremental order multiple rows. In this table I have a Event Trigger to invoke the webhook when I have a **_INSERT_**.

My tables in hdb_catalog schema:
- Table _event_log_ where events are order by _created_at_. I extract _'index1'_ from payload field.

- Table _event_invocation_logs_ order by _created_at_. I extract _'index1'_ from payload field.

In table _event_invocation_logs_ the order of invocation is copletely diferentte from _event_log_. Why? Is there a reason for this happen?
Note: The number of trys it's one for all events.
Contributor guide
Research direction
Start by reproducing the reported inserts and compare ordering in the hdb_catalog event_log and event_invocation_logs tables, using the payload's index1 and created_at values. Read the event-trigger invocation behavior and document whether invocation order is guaranteed; done means the ordering behavior is explained and any required change is scoped with a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100