# Local routines

A local routine asks Nock to do a specific job on a schedule or after your computer has been idle. When it is due, Nock starts a background worker and reports the result. A routine is not a [reminder](/nock/reminders), a one-off task, or a [cloud routine](/nock/cloud-routines): local routines run on this computer and depend on Nock being open.

## Create or turn on a routine

Open **Settings → Routines** to switch on a built-in routine or choose **New routine**. You can also ask Nock to create or enable one, such as “Every weekday at eight, check my calendar and tell me what needs attention.” Nock shows an approval card with the routine's schedule and work before setting it up or turning it on.

Review the schedule, time zone, and what the routine will do. Start with a read-only request. You can also choose **Run now** to test a routine without waiting for its next scheduled time. Use the routine's switch to pause it; choose its remove action if you want it out of your list. Removed built-ins can be restored from **Show removed routines**.

## When it runs

Local routines can run at a scheduled time or once after you have been away for the idle period you chose. A routine does not run when an app opens. The computer must be awake and Nock must be open. If a scheduled run was missed while Nock was closed or the computer was asleep, it can run once when you return within two hours; after that it is skipped rather than replayed several times.

Only one routine runs at a time. A due run waits while you are talking to Nock or while the available background workers are busy. Check its row in **Settings → Routines** for the next run and recent result.

## Review results and approval requests

Routine results appear in the notch; the full result is also available in **Tasks**. That task entry is a run record, not the routine's schedule or configuration. A routine may report that it skipped a run, needs your approval, or hit a usage or connection problem. Read the result before trying the same work again.

Routine workers are instructed to prepare information and drafts, not send, post, publish, delete, or buy. Actions that need your approval wait for a card; if you do not respond, that step is skipped and the routine reports what it could finish. Your access mode affects approval behavior. See [Nock agent access modes](/nock/agent-access) and [Task approvals](/nock/task-approvals).

## Plan and computer requirements

Routines that run background work require a plan that includes building, such as Nock Pro or higher. You can view or edit routines without that access, but Nock will explain when a routine cannot run under your current plan. Each local run uses the plan's background-work allowance.

Your computer must remain available for local runs. For work scheduled to run remotely, see [Cloud routines](/nock/cloud-routines) and [Cloud bots](/nock/cloud-bots); those are separate services and have different availability and usage rules.