I got an email this morning from supabase saying that I'm exceeding my Disk I/O budget. I check supabase and I can see that on the 6th April, I randomly started getting 1.4k edge function invocations per day.
This project is on the supabase free plan, and it's a website that has never left localhost. Nobody has access to it apart from me, and I haven't logged into supabase for 3 weeks, or used this project in any way.
It turns out, this is because of a CRON job called stripe-sync-worker, which is part of the stripe-sync-engine that I'd integrated 3 weeks ago, that is firing the stripe-worker edge function. Somehow on 6th April it had randomly changed its schedule to fire every minute.
The CRON job and the edge functions are all part of the stripe-sync-engine integration. I haven't edited any of them, all I did was turn on the integration 3 weeks ago.
I got an email this morning from supabase saying that I'm exceeding my Disk I/O budget. I check supabase and I can see that on the 6th April, I randomly started getting 1.4k edge function invocations per day.
This project is on the supabase free plan, and it's a website that has never left localhost. Nobody has access to it apart from me, and I haven't logged into supabase for 3 weeks, or used this project in any way.
It turns out, this is because of a CRON job called stripe-sync-worker, which is part of the stripe-sync-engine that I'd integrated 3 weeks ago, that is firing the stripe-worker edge function. Somehow on 6th April it had randomly changed its schedule to fire every minute.
The CRON job and the edge functions are all part of the stripe-sync-engine integration. I haven't edited any of them, all I did was turn on the integration 3 weeks ago.