Moving Daily Jobs from GitHub Actions to cron‑job.org for a Render‑Free API

Description and use

<h1> Moving Daily Jobs from GitHub Actions to cron‑job.org for a Render‑Free API </h1> <p><strong>TL;DR:</strong> I replaced the internal setTimeout‑based schedulers and GitHub Actions cron with an external cron‑job.org trigger plus a lightweight “wake” endpoint. This prevents the Render free instance from sleeping and guarantees daily email, report, and cleanup jobs run on schedule.</p> <h2> The Problem </h2> <p>Our API (<code>playamxcrm-api</code>) runs on Render’s free tier. Render idles the container after ~15 minutes of inactivity, which means any <code>setTimeout</code>/<code>setInterval

Problem

<h1> Moving Daily Jobs from GitHub Actions to cron‑job.org for a Render‑Free API </h1> <p><strong>TL;DR:</strong> I replaced the internal setTimeout‑based schedulers and GitHub Actions cron with an external cron‑job.org trigger plus a lightweight “wake” endpoint. This prevents the Render free instance from sleeping and guarantees daily email, report, and cleanup jobs run on schedule.</p> <h2> The Problem </h2> <p>Our API (<code>playamxcrm-api</code>) runs on Render’s free tier. Render idles the container after ~15 minutes of inactivity, which means any <code>setTimeout</code>/<code>setInterval

Outcome

<h1> Moving Daily Jobs from GitHub Actions to cron‑job.org for a Render‑Free API </h1> <p><strong>TL;DR:</strong> I replaced the internal setTimeout‑based schedulers and GitHub Actions cron with an external cron‑job.org trigger plus a lightweight “wake” endpoint. This prevents the Render free instance from sleeping and guarantees daily email, report, and cleanup jobs run on schedule.</p> <h2> The Problem </h2> <p>Our API (<code>playamxcrm-api</code>) runs on Render’s free tier. Render idles the container after ~15 minutes of inactivity, which means any <code>setTimeout</code>/<code>setInterval

Evidence

Moving Daily Jobs from GitHub Actions to cron‑job.org for a Render‑Free API

Source