i have a db function which calls a supabase egde function which triggers a task - this runs on a column value change per row on one of my db tables - i noticed that if i update the rows, say, 10 at a time, the tasks are successfully triggered, but if i do it say, 100 at a time, it doesn't - is this a known behaviour? or should i investigate something happening on my db side?
#triggering 100 events from supabase edge functions
fickle parcel
loud tapir
Ah yes I'm very familiar with this from our v2 Supabase triggers. If you edit lots of rows at once the Supabase database webhooks can fail.
If you look in Supabase at the net schema in your database you can see the webhook calls. I think you'll find that some of them have timed out, or failed in some other way.
It says in the known limitations it can handle max of 200 per second: https://supabase.com/docs/guides/database/extensions/pg_net#limitations
I think there's a way to increase the timeout which I found helped increase the throughput, but I can't remember how to do that
dawn wagon
@fickle parcel I also had this issue but it seems they fixed it if you upgrade your Supabase project through the dashboard: https://github.com/supabase/pg_net/issues/86
