agentleFS
charanjit-singhcharanjit-singh/lovable-skills/skills/background-jobs-and-cron/SKILL.md

background-jobs-and-cron

Skill10 starsChanged 6 months agoMITView on GitHub

Use when scheduling background work: cron jobs, digest emails, cleanup tasks, pg_cron, Supabase scheduled edge functions, or job queues. Not for synchronous user-facing API in the request path.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No long blocking in HTTP request — enqueue job instead.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Background jobs and cron

This is the overview / decision guide. Once you've picked an approach, the deep dives are:

  • pg-cron-scheduled-jobs — pg_cron syntax, monitoring, locking, idempotency.
  • pg-cron-with-pg-net-edge — cron jobs that call edge functions via HTTPS.
  • pg-cron-recipes — copy-pasteable cookbook (cleanup, retries, digests, expirations).

Choose mechanism

NeedApproach
Simple periodic task (daily cleanup)pg_cron or Supabase scheduled Edge Function
Heavy / external APIsEdge function invoked on schedule
User-specific delayed workscheduled_at column + cron polls due rows
High volume queueExternal queue (future); start with jobs table

jobs table pattern

create table public.jobs (
  id uuid primary key default gen_random_uuid(),
  type text not null,
  payload jsonb not null default '{}',
  run_at timestamptz not null default now(),
  status text not null default 'pending' check (status in ('pending','running','done','failed')),
  attempts int not null default 0,
  last_error text,
  created_at timestamptz default now()
);
create index jobs_pending_run_at_idx on public.jobs (status, run_at) where status = 'pending';

Cron edge function (every minute):

  1. select * from jobs where status = 'pending' and run_at <= now() limit 10 for update skip locked
  2. Process; set done or failed with backoff (run_at = now() + interval '5 minutes', attempts + 1).

pg_cron (SQL-only tasks)

select cron.schedule('purge-old-logs', '0 3 * * *', $$ delete from public.logs where created_at < now() - interval '90 days' $$);

Enable extension per Supabase project docs; prefer edge function if logic needs secrets/SDKs.

Scheduled edge function

Supabase dashboard → Edge Functions → schedule, or supabase functions deploy with cron config per platform docs.

Rules

  • Idempotent job handlers (safe retry).
  • Max attempts then failed + alert.
  • No long blocking in HTTP request — enqueue job instead.

Avoid

  • setInterval in browser for server work.
  • Duplicate cron without leader lock (for update skip locked or single scheduler).

Checklist

  • Secrets only in edge env
  • Failed jobs visible (admin table or logs)
  • RLS: jobs not client-writable

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.