chore(hasura): explicit timeout on every action + supersede #54#56
Merged
Conversation
Every action in metadata/actions.yaml now has an explicit timeout. Bands
documented in a comment at the top of the file:
10s — local-only sync mutations
30s — DB-bound mutations / lookups against well-warmed tables
60s — read paths that may touch ClickHouse system tables or generate
SQL across the whole cube graph
120s — Cube.js compile-bound queries (cold cache hits 14-30s p99)
180s — first-time table introspection / multi-step gen flows
300s — long-running profiling, LLM-driven generation, big query runs
Notable bumps from the previously-implicit 30s default:
fetch_meta 30 → 120 (supersedes #54 — Cube.js compile)
run_query 30 → 300 (analytical queries on cold caches)
profile_table 180 → 300 (LC probe alone takes minutes on big tables)
fetch_dataset, gen_sql, pre_aggregation_preview, pre_aggregations,
copy_datasource, export_data_models 30 → 60
Hard-tightened where the action is actually trivial:
list_all_teams, manage_query_rewrite_rule, update_member_properties,
update_team_properties, invite_team_member, check_connection,
send_test_alert, create_team stays at 30s but now explicit
create_events stays at 10s
Closes #54 (fetch_meta timeout) — that PR can be closed in favor of
this one which lands the same fix plus the rest of the audit.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3 tasks
firsi
approved these changes
May 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Every action in `metadata/actions.yaml` now has an explicit `timeout`. Replaces the implicit Hasura default (30s) which was both too short for compile/profile paths (causing the recent "save cube times out" symptom) and too generous for trivial mutations.
Bands
```
10s — local-only sync mutations
30s — DB-bound mutations / lookups against well-warmed tables
60s — read paths that may touch ClickHouse system tables or generate
SQL across the whole cube graph
120s — Cube.js compile-bound queries (cold cache hits 14-30s p99)
180s — first-time table introspection / multi-step gen flows
300s — long-running profiling, LLM-driven generation, big query runs
```
Changes
Supersedes
Closes #54 — that PR raised `fetch_meta` 30 → 120 in isolation. This PR rolls that fix in alongside the rest of the audit. Either merge this and close #54, or merge #54 first and rebase this.
Test plan
🤖 Generated with Claude Code