S
Supabase•2mo ago
Adil

Cron jobs not executing after DB reset

We have 2 projects running, one development and one prod. I have my cron jobs running in development and they fire consitently. However, when i duplicate them to production they dont fire. Not even a simple test case, suchas : 
[{"idx":2,"jobid":3,"schedule":"* * * * *","command":"SELECT 'test executed at ' || NOW();","nodename":"localhost","nodeport":5432,"database":"postgres","username":"postgres","active":true,"jobname":null}]
[{"idx":2,"jobid":3,"schedule":"* * * * *","command":"SELECT 'test executed at ' || NOW();","nodename":"localhost","nodeport":5432,"database":"postgres","username":"postgres","active":true,"jobname":null}]
The PG cron extension is active and installed. I tried creating a log table, nothing was being sent. I tried checking job_details but it is not being populated. Anyone know why this is the case?
1 Reply
garyaustin
garyaustin•2mo ago
https://supabase.com/docs/guides/troubleshooting/pgcron-debugging-guide-n1KTaz Some debugging steps.
Supabase Docs | Troubleshooting | pg_cron debugging guide
Supabase is the Postgres development platform providing all the backend features you need to build a product.

Did you find this page helpful?