Menu

Supabase Realtime not firing? 7 checks when postgres_changes sends nothing
📰

Supabase Realtime not firing? 7 checks when postgres_changes sends nothing

DEV Community: javascript·Ahmed Hassan Yaseen·9 days ago
#OwKUGMws
#devtojavascript#devto#dev#table#supabase
Reading 0:00
15s threshold

You subscribe to a table, the status callback says SUBSCRIBED , a row changes in the database, and your app hears nothing. No error in the console, no event, just silence.

Supabase's own troubleshooting guide describes exactly this and says the cause is almost always one of a handful of things. Below are the checks in the order I'd run them, with the SQL and code for each. Everything here is taken from the Supabase Postgres Changes docs , their Postgres Changes troubleshooting guide , and their messages not arriving guide , all read on 7 November 2026.

First, a working baseline

This is the shape of a subscription that should fire for every change on one table:

const channel = supabase . channel ( ' todos-changes ' ) . on ( ' postgres_changes ' , { event : ' * ' , schema : ' public ' , table : ' todos ' }, ( payload ) => console . log ( ' Change received: ' , payload ) ) . subscribe (( status ) => console .…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.