Database Webhook Fails Silently Despite All Checks Passing

[akiru6]

Hi everyone,
I've run into a wall with a database webhook that seems to be failing silently, and I'm hoping someone might have an idea for a next step. I've been through all the standard documentation and troubleshooting, but the issue persists.

The Scenario

• Expected Behavior: An INSERT on the public.posts table triggers a database webhook, which then invokes my Edge Function (enrich-community-post).
• Actual Behavior: The record is inserted successfully, but the function is never called. There are no entries in the function logs and no delivery attempts in the webhook logs. The failure is completely silent.

My Debugging Checklist (What I've Already Ruled Out)
I'm confident the issue isn't a simple configuration error, because I've verified the following:
✅ The Edge Function Works: I can call the function directly using curl. It returns a 200 OK and prints logs as expected. The deployment is healthy.
✅ The Database Trigger Exists: An SQL query on information_schema.triggers confirms the INSERT trigger is registered on the posts table.
✅ Row Level Security is Correct: There's an active RLS policy granting SELECT to the supabase_functions_admin role.
✅ Network Permissions are Granted: We ran GRANT USAGE ON SCHEMA net TO supabase_functions_admin; to ensure the function role has the required network access.
✅ The Table is Published: I've checked in the dashboard (Database > Replication) and via SQL that the posts table is part of the supabase_realtime publication.

To prove the issue isn't in my application logic, I deployed this minimal test function. The curl test passes with this code, but the database trigger still fails silently.

// supabase/functions/enrich-community-post/index.ts
import { serve } from "https://deno.land/std@0.168.0/http/server.ts";

console.log("Test function initialized!");

serve(async (req) => {
try {
console.log("Request received!");
const body = await req.json();
console.log("Request Body:", JSON.stringify(body, null, 2));

return new Response(JSON.stringify({ success: true, received_body: body }), {
  headers: { "Content-Type": "application/json" },
  status: 200,
});

} catch (err) {
console.error("Error in test function:", err.message);
return new Response(JSON.stringify({ error: err.message }), {
headers: { "Content-Type": "application/json" },
status: 500,
});
}
});

My Question for the Community
My core question is simple: Why would the Edge Function logs be completely empty after a database insert?

I've proven the function works on its own, and I've proven the database should be sending an event.
But the two are not connecting. Since I've already checked RLS, permissions, and publications, I'm out of ideas for what to check next.

Is there another setting or log I'm missing that could explain this silence?
Has anyone else run into a similar issue and found a solution?

Any guidance on where to look next would be incredibly helpful.
Thanks,
John

[GaryAustin1]

Check the Postgres log for errors.
Use the table UI to check the net schema _http_response table to see if there is useful status coming back from pg_net which the webhook uses.
Make sure if your edge function requires a valid JWT in the Authorization header that you have the webhook send that header (option at end).

Not sure why you bring up publications as you don't mention realtime here and that is not involved with webhooks.

[akiru6]

Hey @GaryAustin1, thank you so much! You were absolutely right.
The issue was that the webhook needed to send the authentication header. I added the Authorization: Bearer [my_service_role_key] to the webhook's settings, and it started working immediately.
Really appreciate the help!

[Rubenburdin]

Just to add a small note for anyone else landing here with silent webhook failures, the net._http_response table Gary mentioned is genuinely useful for debugging these. It stores the actual HTTP response from each pg_net request, so you can see status codes and error messages that don't surface anywhere else in the dashboard.

One other thing worth checking if you hit similar issues in the future: the pg_net background worker has a queue, and if something upstream is misconfigured it can silently drop requests. Running SELECT * FROM net._http_response ORDER BY created DESC LIMIT 10; right after an insert will show you whether the request even attempted to go out and what came back.
Also worth noting that the Authorization header needs the fulll Bearer format, I've seen folks paste just the key without the Bearer prefix and get 401s that look confusing in the response table.
Hope this helps anyone else debugging webhook silence.