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.

referencesprovidersazure.md

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

Task scheduling — Azure

Service mapping

  • Logic Apps — managed scheduled/recurring triggers and low-code workflow orchestration; recurrence trigger maps the distributed scheduler option, and the connector workflow maps the workflow DAG option.
  • Azure Functions Timer trigger — cron-expression scheduled functions; HA managed cron for code-first jobs. Maps the scheduler option.
  • Storage Queues / Service Bus Queues + Functions or workers — the queue holds jobs; the lock/visibility (peek-lock) duration is the lease; a worker pool drains it. Maps pull leasing. Service Bus has dead-lettering built in.
  • Service Bus scheduled messages / message TTL — per-message scheduled enqueue time. Maps the delay queue option.
  • Durable Functions — code-first orchestration with retries/timers (see temporal.md).

When to pick which

Functions Timer trigger for code-first cron; Logic Apps for low-code scheduled workflows and connector-heavy orchestration; Service Bus + workers for priority/sessions and built-in DLQ; Storage Queues for a cheap, simple job queue.

Limits / things that bite (verify against current docs)

  • Service Bus peek-lock default lock is short (e.g. ~30–60 s); renew the lock (the heartbeat equivalent) for long jobs or set a longer lock duration; lock expiry re-delivers.
  • Storage Queues give at-least-once with a visibility timeout but no native DLQ (you build it) and weaker ordering; Service Bus adds sessions (ordering), DLQ, and scheduled messages.
  • Functions Consumption plan has an execution-time cap and cold starts — long or latency-sensitive jobs want Premium/Dedicated or container workers.
  • Per-namespace/throughput quotas apply on Service Bus.

Pitfalls

  • Using Storage Queues and discovering there's no built-in dead-lettering.
  • Leaving the Service Bus lock too short for long jobs → re-delivery and double-runs.
  • Running the Functions Timer trigger as if it guarantees exactly-once firing — make the handler idempotent.
  • Lock-in: Logic Apps / Durable Functions definitions 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