Support Engineer @Supabase | StackOverflow
Nothing here yet.
Yes, this concern is valid, and it comes down to whether the webhook is essential to your logic. This is a better solution if you need to ensure a response from the hook. If you are fine with failures on the webhook, then you can use the default hooks with async behavior is superior. A third option is to have a queue with retries using async logic. You can use supa_queue for that: https://github.com/mansueli/supa_queue
Sorry, a little oversight from me. If you change the $$ in the function or in each command with a different context it will work: RETURNS VOID AS $function$ BEGIN (...) $ function $ LANGUAGE plpgsql; Or on each command: PERFORM cron.schedule( 'process_current_jobs_if_unlocked_job_3', '* * * * *', $command$ SELECT process_current_jobs_if_unlocked(); $command$ ); I'll update the article to fix the example.