cron-job.org
A free online external cron scheduling service that can call HTTP endpoints at minute-level frequency, used to trigger web tasks on a schedule.
Timeline (last 90 days)
cron-job.org is a free online Cron scheduling service that supports scheduling intervals as short as once per minute, with its own servers initiating HTTP requests to the target URL.
cron-job.org has a timeout ceiling of about 30 seconds per request, so the invoked endpoint must return quickly and cannot perform time-consuming tasks.
In the migration plan, the author introduced the external Cron service cron-job.org to call a lightweight endpoint every minute to keep the API alive, and separately trigger the actual daily job at UTC 07:00.
The "fire-and-forget" pattern lets the Web layer's /api/wake endpoint return 200 without blocking and waiting for the backend response, thereby avoiding triggering cron-job.org's 30-second timeout.
This approach counters the free-tier sleep policy through external scheduling plus keep-alive traffic, at the cost of introducing a dependency on a third-party Cron service and generating wake-up traffic once per minute; if cron-job.org fails, the keep-alive chain will be interrupted.
The author downgraded the original GitHub Actions workflow cron-diario.yml to a manual fallback, with the actual scheduling logic taken over by cron-job.org.
All Facts (6)
cron-job.org is a free online Cron scheduling service that supports scheduling intervals as short as once per minute, with its own servers initiating HTTP requests to the target URL.
50%Unverifiedcron-job.org has a timeout ceiling of about 30 seconds per request, so the invoked endpoint must return quickly and cannot perform time-consuming tasks.
50%UnverifiedThe "fire-and-forget" pattern lets the Web layer's /api/wake endpoint return 200 without blocking and waiting for the backend response, thereby avoiding triggering cron-job.org's 30-second timeout.
50%UnverifiedThis approach counters the free-tier sleep policy through external scheduling plus keep-alive traffic, at the cost of introducing a dependency on a third-party Cron service and generating wake-up traffic once per minute; if cron-job.org fails, the keep-alive chain will be interrupted.
50%UnverifiedIn the migration plan, the author introduced the external Cron service cron-job.org to call a lightweight endpoint every minute to keep the API alive, and separately trigger the actual daily job at UTC 07:00.
50%UnverifiedThe author downgraded the original GitHub Actions workflow cron-diario.yml to a manual fallback, with the actual scheduling logic taken over by cron-job.org.
50%