Schedule your AI agent: automatic runs (managed cron)

Published on 2 min read

Set your AI agent to wake up on its own, run at a fixed time or every X minutes, and go back to sleep — without staying online around the clock.

Not every AI agent needs to stay on 24 hours a day. An agent that only summarizes a feed in the morning, or runs a routine every half hour, shouldn't have to hold your plan's RAM the whole time waiting. You can now schedule it: MyBotCloud wakes the agent, calls a path in your code, and puts it back to sleep on its own.

How to set it up

Open the agent under Manage → Schedule (the tab only shows up for AI agent apps) and pick one of two modes:

  • Every day, at a time — a fixed UTC time (e.g. 08:00).
  • Every X minutes — an interval, minimum 15 minutes.

Also set the path to call (e.g. / or /chat — whatever your code responds to) and whether the agent should keep running after the call or go back to sleep.

What happens at the scheduled time

  1. The platform turns the agent on (if it was off).
  2. It waits up to 30 seconds for the agent to become healthy.
  3. It calls the configured path, with a 25-second timeout.
  4. It records the result — success or error, with the time.
  5. If "keep running" is not checked, it turns the agent back off.

A checker runs once a minute, so the actual run can land up to ~1 minute after the exact time — not a millisecond-precision clock, but reliable enough for routines that don't depend on the exact second.

The tab shows the last run (success, or the error if something went wrong) and the next run, always in UTC.

Why this matters

For anyone on a smaller plan, an agent that spends most of the day asleep frees up RAM from your plan's pool for your other apps. And because the wake/sleep cycle is intentional, it never triggers a "app is down" alert for anyone with crash alerts configured — the platform knows how to tell a scheduled shutdown apart from a real failure.

Still stuck? Open a ticket in Support in the dashboard.

  • ai agents
  • scheduling
  • cron
  • automation

← Back to the blog