Cannot Create Event Trigger on Hasura #10795
Description
Version Information
Server Version:
CLI Version (for CLI related issue):
v2.47.0-ce
Console asset version:
1742224660257
Environment
Cloud (Aptos Labs — Managed Hasura)
What is the current behaviour?
When attempting to create an Event Trigger in Hasura, the operation fails and returns a transaction error.
Hasura appears to execute the following internal statement:
BEGIN ISOLATION LEVEL READ COMMITTED READ WRITE
What is the expected behaviour?
Event Triggers should be created successfully without Hasura failing to begin a read-write transaction.
Metadata creation should proceed normally.
How to reproduce the issue?
1. Open Hasura Console in the Aptos-managed Hasura instance.
2. Navigate to: Events → Triggers.
3. Click Create and fill in a valid trigger configuration (name, table, and webhook URL).
4. Click Save.
5. Hasura returns the error shown above.
Screenshots or Screencast
Please provide any traces or logs that could help here.
cannot set transaction read-write mode during recovery
status_code: 0A000
statement: BEGIN ISOLATION LEVEL READ COMMITTED READ WRITE
Any possible solutions/workarounds you're aware of?
No workarounds found so far.
I attempted:
• Cleaning/reloading Hasura metadata
• Recreating the target table
• Restarting the instance
None of these resolved the issue.
Keywords
event trigger
transaction read-write mode
0A000
BEGIN ISOLATION LEVEL READ COMMITTED READ WRITE
Aptos Hasura
FatalError