Index of every page on this site: llms.txt
All skills
proyecto26 avatar

/task-scheduling

@228d57d
Run it yourself

This skill should be used when the user designs a "task scheduler", "job scheduler", "job queue", "cron at scale", "distributed cron", "delayed / scheduled / recurring tasks", a "worker pool", reaches for "Celery / Sidekiq / Airflow", or wrestles with "task leasing", visibility timeouts, job priorities, fairness, or duplicate task execution. Use it whenever work must run later, on a schedule, or be reliably leased to a pool of workers, even if the user doesn't say "scheduler". (For plain queue transport and delivery guarantees, that is `messaging-streaming`.)

Use this Skill: https://skilld.dev/gh/proyecto26/system-design-skills/task-scheduling

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesprovidersgcp.md

≈535 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Task scheduling — GCP

Service mapping

  • Cloud Scheduler — fully-managed cron; fires HTTP, Pub/Sub, or App Engine targets on a crontab. Maps the distributed scheduler option (HA, no leader to run).
  • Cloud Tasks — managed task queue with explicit dispatch to an HTTP/App Engine target, per-task scheduled time (delay), rate/concurrency limits, and automatic retries with backoff. Maps pull/push leasing + the delay queue + per-queue fairness/rate options.
  • Workflows — managed orchestration of steps/services with retries. Maps the workflow DAG option for multi-step jobs (see also temporal.md).
  • Pub/Sub — the transport when fan-out delivery is needed (→ messaging-streaming).

When to pick which

Cloud Scheduler for cron/recurring triggers; Cloud Tasks when you need per-task delays, rate limiting, and built-in retries to a worker endpoint; Workflows when multi-step orchestration is the hard part. Cloud Scheduler → publishes a message; Cloud Tasks → dispatches to your handler — combine them.

Limits / things that bite (verify against current docs)

  • Cloud Tasks has per-queue dispatch rate and max-concurrent-dispatch caps (your fairness/throttle knob) and a max task schedule time / retention window (far-future delays beyond it need storing and re-enqueue).
  • Cloud Tasks dispatch is at-least-once with a per-task dispatch deadline (the lease/visibility equivalent) — exceed it and the task is retried → make handlers idempotent.
  • Cloud Scheduler fires at-least-once — a tick can double-fire on retry; make the target idempotent (key by scheduled time).
  • Targets are HTTP/Pub/Sub endpoints, so worker scaling is your handler's concern (Cloud Run / GKE autoscaling).

Pitfalls

  • Setting the Cloud Tasks dispatch deadline shorter than the job → retries and double-runs.
  • Assuming Cloud Scheduler guarantees exactly-once firing (it doesn't).
  • Using Cloud Tasks for far-future delays beyond its schedule horizon.
  • Lock-in: Cloud Tasks/Scheduler/Workflows configs don't port to other clouds.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts24d3 checks · Risk SAFE
  • Gen Agent Trust Hub24d

    The skill provides architectural guidance for designing task scheduling systems. No security issues were detected.

  • Socket24d

    No alerts

  • Snyk24d

    Risk: LOW · No issues

Signed by skilld at 228d57d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 4 weeks ago

README badge

README badge for proyecto26/system-design-skills/task-scheduling