permission denied for sequence net.http_request_queue_id_seq
edge functionsPostgRESTI’m running a production SaaS on Supabase and I’m using pg_cron to trigger net.http_post() daily (for subscription renewals and deactivation logic via an Edge Function).
This setup worked reliably for a long time, but recently it started failing with:
No code or schema changes were made on my side.
From the logs, the job runs via pg_cron and fails during the internal insert into net.http_request_queue, which suggests permissions on internal sequences were reset or tightened (possibly after an extension or infrastructure update).
My concern is long term reliability, since this is customer-critical logic and I can’t afford to manually re grant permissions after internal changes.
Questions:
This setup worked reliably for a long time, but recently it started failing with:
permission denied for sequence net.http_request_queue_id_seqNo code or schema changes were made on my side.
From the logs, the job runs via pg_cron and fails during the internal insert into net.http_request_queue, which suggests permissions on internal sequences were reset or tightened (possibly after an extension or infrastructure update).
My concern is long term reliability, since this is customer-critical logic and I can’t afford to manually re grant permissions after internal changes.
Questions:
Is pg_cron + net.http_post() considered a supported/stable pattern for production workloads?Are internal schema permissions (like net.*) expected to change during updates?Is the recommended production approach to move scheduled jobs to Supabase Scheduled Edge Functions instead?
