How-to guide

Schedule automations

Ask Nawa to repeat a task with a clear schedule, timezone, data source and desired output. For example: “Every weekday at 9 am Asia/Dubai, search for the latest AI announcements and produce a short report with sources.” The chat menu's Automate action is another starting point for turning existing work into a recurring task.

Durable automation changes require an approval card, including in Bypass permissions mode. Read what will run and where its output will go before accepting.

Check activation

An automation requested as active is validated before it activates. Testing means validation is still running, not that the schedule is ready. A failed validation leaves it needing attention. Explicit Draft and Paused requests stay inactive.

Open Automations in the sidebar to inspect the saved task, schedule, state and runs. Confirm it is active and the timezone is right. Do not assume the chat's acknowledgement alone proves activation.

Change or stop it

Ask Nawa to change the named automation, pause it, resume it or delete it. A changed active execution contract must validate again. Renaming an otherwise paused task does not resume it. A result from an older validation cannot reactivate a task you have since paused or edited.

If a run fails, open its run details, inspect the actual error and correct the cause: a disconnected service, moved file or expired credential, for example. Ask for another test before relying on the schedule. Pausing stops future scheduling; stopping a currently running task is a separate action.

The machine hosting Nawa's scheduler and engine must be available. Closing the main window and quitting the application are different: the background engine can remain running when the window closes. Do not count on local schedules while the machine is asleep or shut down.