Skip to main content
A schedule runs an Agent on a cadence without anyone starting it by hand: a morning AR aging summary, an hourly check for overdue invoices, or a monthly vendor-bill roundup. Follow the work in run history and any linked Task.

​
Add a schedule

Open Scheduled from the profile menu for recurring task schedules and Agent schedule triggers across the workspace. Open an Agent’s Schedules tab to focus on that Agent. New schedule creates a recurring task schedule. To start an Automation with a Schedule trigger, configure that trigger in the Agent builder and publish the Agent. Both kinds appear on Scheduled.
1

Open Schedules

Go to Agents, open the Agent, and switch to Schedules, or open Scheduled from the profile menu.
2

Click New schedule

Select New schedule to add a recurring run.
3

Set the cadence

Choose how often it runs — minutes, hourly, daily, weekly, or monthly — and set the time zone so runs fire at the hour you expect.
4

Save

Save the schedule. The agent now runs on that cadence and creates a task for each run.
The agent must be Live (published) with a runnable start step before a schedule can run it. See Publishing & lifecycle.

​
Cadences

The recurrence type and time zone are set in the Schedule details dialog, the same controls used for recurring tasks.

​
Manage an existing schedule

Each schedule in the list has its own controls:
  • Run now — trigger an off-cycle recurring-task run immediately, without waiting for the next scheduled time.
  • Pause / Resume — temporarily stop a schedule from firing, then turn it back on. Paused schedules keep their settings. The same control is on the schedule trigger node in the visual builder, which is handy when an agent has several schedules and you only want to pause one.
  • Edit — change the cadence, time zone, or inputs.
  • Delete — permanently remove a recurring task schedule and stop its future runs. Existing tasks and agent runs stay in place.
Where Edit opens depends on how the schedule was set up. A schedule built from a Schedule trigger in the agent opens in the visual builder so you can adjust or remove the trigger step. A recurring task schedule opens in the Schedule details dialog, where it can also be deleted.

​
How schedules relate to tasks

When assigning Agent work as a Task, the two future-run modes are:
  • Scheduled — a one-time run set for a future time. Upcoming one-time tasks show in the Tasks Scheduled view and on the team Overview.
  • Recurring — a saved schedule that runs on a cadence and produces a task each time. Manage these on the separate Scheduled page or the Agent’s Schedules tab.
Tasks created by recurring task schedules follow the normal lifecycle: Queued → In Progress → Needs Review → Complete. If the Agent’s team requires human confirmation, finished work waits in Needs Review until a person approves it. An Agent trigger’s execution can be inspected in run history whether or not it has a linked Task.

​
Run As for scheduled runs

A scheduled run starts with no one sitting at the keyboard, so the agent needs to know which NetSuite user identity to run under. That is the Run As setting on the agent’s trigger.
1

Configure Run As

On the agent’s trigger, set Run As to the user whose NetSuite authorization the run should use. Automated agents can’t be published until Run As is configured.
2

Confirm consent

Running as a fixed user requires that user’s consent. Watch for states like Needs Run As, Needs consent, Wrong user, or Not available, and resolve them before relying on the schedule.
Scheduled Agent runs use the authorized Run As identity and the Agent’s configured write policy. A tool set to Allow can change records without a confirmation step. Review the permitted tools and approval requirements before enabling the schedule. The plain-chat Write actions setting does not replace an Agent’s governance.

​
Frequently asked

Open the schedule’s History or the Agent’s Runs view to see which executions started and their current status. Check active runs before starting another manually, and use Cancel on a run if needed.
No. Pausing only stops future runs. Past runs and their tasks stay in run history.
No. Deleting removes the schedule and stops future runs, but existing tasks and agent runs remain available. A run already in progress continues.
Schedules suit Automation agents built on a Schedule trigger. Assistant and Workforce agents are chat-first; to run one on a cadence, set up a recurring task for it instead.
The most common causes are an unconfigured Run As, a missing connection, the agent being in Draft, or a paused schedule. See Common issues.

​
Next steps

Triggers

How Chat, Form, Schedule, Webhook, and Email triggers start an agent.

Run history & traces

Track every scheduled run and inspect its step-by-step trace.

Working with tasks

Set recurrence, assignees, and reviewers on the tasks schedules create.

Authorize NetSuite

Set the per-user authorization a Run As schedule depends on.