Describe the bug
Navigating to a newly made database's triggers loads for a while and then renders a warning with unformatted 404 page that says to contact support.
To Reproduce
Steps to reproduce the behavior:
0. supabase init, supabase start
- Go to http://localhost:54323/project/default/database/triggers
- See error
Expected behavior
Show the db triggers.
Screenshots
If applicable, add screenshots to help explain your problem.

System information
Rerun the failing command with --create-ticket flag.
- Ticket ID: I don't know if it's applicable since it's not a specific command in the cli
- Version of OS: macOS Sonoma 14.4.1
- Version of CLI: 2.12.0
- Version of Docker: [e.g. v25.0.3]
- Versions of services:
SERVICE IMAGE │ LOCAL │ LINKED
─────────────────────────┼──────────────────┼─────────────
supabase/postgres │ 15.6.1.115 │ 15.6.1.115
supabase/gotrue │ v2.168.0 │ v2.168.0
postgrest/postgrest │ v12.2.3 │ v12.2.3
supabase/realtime │ v2.34.7 │ -
supabase/storage-api │ v1.17.1 │ v1.17.1
supabase/edge-runtime │ v1.67.0 │ -
supabase/studio │ 20250130-b048539 │ -
supabase/postgres-meta │ v0.84.2 │ -
supabase/logflare │ 1.4.0 │ -
supabase/supavisor │ 1.1.56 │ -
Additional context
If applicable, add any other context about the problem here.
- Browser is Chrome, also doesn't work in Safari
Describe the bug
Navigating to a newly made database's triggers loads for a while and then renders a warning with unformatted 404 page that says to contact support.
To Reproduce
Steps to reproduce the behavior:
0.
supabase init,supabase startExpected behavior
Show the db triggers.
Screenshots
If applicable, add screenshots to help explain your problem.
System information
Rerun the failing command with
--create-ticketflag.SERVICE IMAGE │ LOCAL │ LINKED
─────────────────────────┼──────────────────┼─────────────
supabase/postgres │ 15.6.1.115 │ 15.6.1.115
supabase/gotrue │ v2.168.0 │ v2.168.0
postgrest/postgrest │ v12.2.3 │ v12.2.3
supabase/realtime │ v2.34.7 │ -
supabase/storage-api │ v1.17.1 │ v1.17.1
supabase/edge-runtime │ v1.67.0 │ -
supabase/studio │ 20250130-b048539 │ -
supabase/postgres-meta │ v0.84.2 │ -
supabase/logflare │ 1.4.0 │ -
supabase/supavisor │ 1.1.56 │ -
Additional context
If applicable, add any other context about the problem here.