Skip to main content
Waldo can turn work from a chat into a task schedule that runs again on a timer after the chat ends. Use a schedule for recurring work, such as a daily refresh of a results table or an hourly data transformation. In the Wherobots API, a schedule is called a trigger.
Waldo is in public preview. It’s available in every Organization Edition, including the free Professional Edition trial. Features and limits may change before general availability.

How scheduling works

1

Describe the recurring task

Say what the task does, how often it runs, and the time zone. For example: “Every day at 6:00 AM Pacific, update the building counts per H3 cell for new footprints.”
2

Waldo writes the script

Waldo writes a Python script and saves it to My Files. Each run processes one time window, from the previous scheduled time to the current one.
3

Waldo creates the schedule paused

Waldo sets the interval or cron expression, region, runtime size, and timeout. You approve the schedule in the chat before Waldo creates it.
4

Waldo tests one window

With your approval, Waldo starts a single run for a time window you confirm, then reads the logs and shows you the result.
5

Waldo resumes the schedule

When the test output is correct and you approve, the schedule becomes Active and runs on its own.
To run tasks in sequence or as a DAG, contact product@wherobots.com.

Manage schedules with Waldo

In any chat, you can ask Waldo to:
  • list your Organization’s schedules and their state,
  • show run history and read the logs for a run,
  • change a schedule’s timing, script, runtime size, or notification emails,
  • pause, resume, or archive a schedule, or
  • run a schedule now for a time window you choose, or rerun a failed window.
Changes, runs, and reruns need your approval. You can also manage every schedule on the Scheduled Tasks page in Wherobots Cloud, which shows each schedule’s next run and its Upcoming runs.

What to know about schedules

  • Each run is billed. Scheduled runs use compute at your normal rates, even when no one has Waldo open.
  • Space runs at least 15 minutes apart. The schedule’s interval or cron expression must create runs that are at least 15 minutes apart. For example, an interval of 15 minutes or more, or a cron expression such as */15 * * * *.
  • Schedules run scripts. A schedule runs a Python script or JAR. You can’t schedule platform tasks, such as RasterFlow tasks, directly.
  • The script must exist when you save the schedule. When a schedule is created or changed, Wherobots checks that its script exists and that you can read it. Waldo saves the script to My Files first.
  • Each run reads the script file. If you or Waldo edit the script, later runs use the new version. To keep a version fixed, save it under a new name and point the schedule to it.
  • Runs use your identity. A schedule that Waldo creates runs as you, with your data permissions.
  • Failures stop the schedule. Wherobots sets a schedule to Auto-disabled after 5 consecutive failed scheduled runs. Ask Waldo to read the failed run’s logs, fix the script, and resume the schedule.
For details, see Scripts and processing windows and Monitor and recover.

Troubleshooting