render-cron-jobs
Configures and troubleshoots scheduled tasks on Render using cron job services. Use when the user needs to run something on a schedule, write a cron expression, set up a periodic job, migrate from Heroku Scheduler, choose between cron jobs and background workers, or fix a cron that isn't firing. Trigger terms: cron job, scheduled task, periodic job, cron expression, schedule, run every, timer, Heroku Scheduler migration.
- License 许可
- MIT
- 最近更新
- 2026-08-25
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- render-cron-jobs
- license
- MIT
- metadata
- { "author": "Render", "version": "1.0.0", "category": "compute" }
- description
- Configures and troubleshoots scheduled tasks on Render using cron job services. Use when the user needs to run something on a schedule, write a cron expression, set up a periodic job, migrate from Heroku Scheduler, choose between cron jobs and background workers, or fix a cron that isn't firing. Trigger terms: cron job, scheduled task, periodic job, cron expression, schedule, run every, timer, Heroku Scheduler migration.
- compatibility
- Render cron job services
02 资源文件 3
- 参考文档agents/openai.yaml210 B
- 参考文档references/cron-patterns.md2.6 KB
- 参考文档references/migration-from-scheduler.md2.7 KB
03 SKILL.md 正文
Render Cron Jobs
This skill covers Cron Job services on Render: how schedules run, what the platform guarantees, and how they differ from workers and workflows. Pair it with Blueprint and deploy skills when authoring render.yaml or Dashboard settings.
When to Use
- Scheduled work that starts on a cron, runs a command, and exits when finished
- Choosing between cron, background worker, or workflow for periodic or long-running jobs
- Blueprint fields for
type: cron,schedule, and commands - Constraints: no disk, single concurrent run, 12-hour max duration, private-network outbound only
- UTC scheduling pitfalls (expressions are not local time)
Expression cheat sheets, framework startCommand examples, and Heroku Scheduler migration mapping live under references/.
Configuration
- Schedule: a cron expression evaluated in UTC, not the team’s local timezone. All times in the Dashboard and Blueprints are UTC.
- Command: any valid Linux shell command or bash script path. The process must exit when work is done—billing is based on run duration (prorated by the second).
- Source:
- Git repository — Render builds on push (same deploy model as other repo-backed services); the built artifact runs on each scheduled invocation.
- Prebuilt Docker image — the image is pulled before each run and is not retained between runs (no warm cache of the image layer set across invocations in the same way as a long-lived service).
Constraints
- No persistent disk — cron job services cannot provision or attach Render persistent disks; plan for object storage or databases instead.
- Single-run guarantee — at most one active run per cron service at a time. A new scheduled tick does not start a second overlapping instance.
- Maximum run length: 12 hours per invocation.
- Pricing: $1/month minimum per cron job service; usage is prorated by the second beyond plan/minimum rules that apply to your account.
- Private network: cron jobs can send traffic to other services on the private network; they cannot receive inbound private-network connections (no internal hostname for accepting traffic from other services).
Execution Behavior
- Manual “Trigger Run” while a run is active: Render cancels the active run, then starts a new one.
- New Git build / deploy does not affect a run already in progress—the in-flight process keeps using the revision it started with until it exits.
- Docker-based crons: the image is pulled fresh for each run; do not assume layer or image reuse across invocations like a continuously running container.
- UTC everywhere: cron expressions and “midnight” in docs mean UTC. A common mistake is copying a local-time schedule into the expression without converting to UTC.
Cron vs Worker vs Workflow
| Need | Use | Why |
|---|---|---|
| Periodic task under 12h | Cron Job | Scheduled, simple, exits when done |
| Continuous job processing | Background Worker | Always running, polls a queue |
| Periodic but over 12h | Background Worker | No 12h cron run ceiling |
| Scheduled parallel compute | Cron Job + Workflow | Cron triggers workflow runs on a schedule; workflows fan out or orchestrate parallel steps |
Blueprint Configuration
Cron services use type: cron with a schedule and the usual build/start and env wiring:
services:
- type: cron
name: nightly-cleanup
schedule: "0 * * * *" # hourly at minute 0 — must be quoted in YAML
buildCommand: pip install -r requirements.txt
startCommand: python cleanup.py
envVars:
- key: DATABASE_URL
fromDatabase:
name: my-db
property: connectionString
schedule: standard five-field cron (minute hour day-of-month month day-of-week), UTC.buildCommand/startCommand: same roles as other non-Docker services; Docker images use image + start command as configured for image-backed crons.envVars: same patterns as web services and workers (secrets, linked databases, etc.).
YAML note: the schedule value must be quoted so characters like * are not parsed as YAML aliases or flow syntax.
Common Patterns
- Database cleanup — archive or delete stale rows on a schedule
- Report generation — build CSV/PDF and upload to object storage or email
- External API sync — pull or push batches on an interval
- Cache warming — hit endpoints or rebuild caches before peak traffic
- Scheduled emails — digest or reminder sends driven by cron + mail/API
References
| Topic | File |
|---|---|
| Expression examples, framework commands, errors, env vars | references/cron-patterns.md |
| Heroku Scheduler → Render mapping, blueprint example | references/migration-from-scheduler.md |
Related Skills
- render-deploy — First-time deploy, service creation, Dashboard flow
- render-blueprints — Full
render.yamlschema, previews, common mistakes - render-background-workers — Long-lived processes, queues, no 12h cap
- render-workflows — Orchestrated and parallel jobs, often triggered on a schedule from cron
04 同仓库更多 Skills
syllabus
Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.
pulse
Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.
patent
Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.
notebooklm
Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio/Video Overviews, Mind Maps, Reports incl. Briefing Doc/Study Guide/FAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.
litreview
Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed/OpenAlex (or Consensus) query.
grants
NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance/Innovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget/scope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.