> ## Documentation Index
> Fetch the complete documentation index at: https://docs.begin.eu/llms.txt
> Use this file to discover all available pages before exploring further.
# Loops
> Run Begin AI on a schedule or when something happens, and share what it does with everyone who can see it.
A loop runs Begin AI on its own: on a schedule, or when something happens, such as a shift being
created. It reads and changes your workspace with its owner's access. Loops replaced Scheduled
tasks: every one became a loop with its name and run history, and a bookmarked scheduled-task
link still opens it.
**Loops** has its own role permission. Managers and administrators have it by default; if you
cannot see **Loops** in the sidebar, ask an administrator to give your role access.
## Create a loop
Start from **New loop** on the **Loops** page.
**On a schedule** reads as one sentence, for example "Every 2 weeks on Monday at 09:00, starting
14 September 2026", in your workspace's timezone. **When something happens** waits for one of
the workspace's events, such as a shift being created, narrowed to a position, a location or a
person.
Write the instructions yourself, or choose **Configure with agent** to draft them with Begin AI.
Instructions are required before you can publish; a title or event details do not replace them.
Turn **Web search** on or off, add a connector such as **Payroll integrations**, and set
**Changes** to **Never** or **Apply everything**.
**Publish** turns your draft into the version that runs.
Or ask **Begin AI** (Cmd / Ctrl + J):
Create a loop that checks tomorrow's schedule every evening and flags anything still unpublished.
Begin AI asks first, and the loop it files starts with no web access, changes or connectors:
turn those on from the **Loops** page.
## Know who authorises a change
Edit access lets you change a loop's setup; only its **owner**'s permissions ever run it. **Who
can edit** is set by the owner or an administrator. Publishing makes a new version live: the
owner's publish takes effect at once; anyone else's becomes a pending revision, and the loop
keeps its last authorised version until the owner authorises it. The owner or publisher may
discard it instead. **Published versions** lists every one; **Restore** prepares a revision the
owner authorises, like any change. A new owner pauses it the same way, clearing web search,
changes and connectors until they authorise it.
Before asking Begin AI to edit a loop with a pending revision, authorise or discard that
revision. AI edits start from the last authorised setup.
## Run it, and see what happened
**Run now** starts one straight away. For an event loop, **Run loop on…** picks an item, such as
a shift or a person, as if the event had just happened to it.
**Run history** lists every run's outcome; opening one shows the instructions used, its
transcript and changes made. New loop runs share their results with everyone who can see the
loop. Conversations carried over from Scheduled tasks, including their replies and attachments,
remain private to their original creator.
Choose **Reply** to open a private follow-up chat only you and Begin AI see. This also applies
when you open a run from the AI sidebar. A deleted transcript cannot be replied to.
**Needs attention** means the loop stopped before a step that always needs a person; changes
already made are kept. That step's card is cancelled once the run closes, so you do it yourself
instead.
If a run is **Skipped** because its saved version has no instructions, edit the loop, add
instructions and **Publish** a new version. Choose **Run now** for a scheduled loop, or **Run loop
on…** and select an item for an event loop. Earlier runs stay in the history and are not replayed
automatically.
## Pause, duplicate, hand over or delete
From each loop's menu:
| To… | Choose |
| ----------------------------------------------------------- | ------------------------ |
| Stop or restart it without losing its setup | **Disable** / **Enable** |
| A paused copy, even of a loop you cannot edit | **Duplicate** |
| Hands it over; pauses until the new owner authorises it | **Change owner** |
| Remove it and its run history for everyone who could see it | **Delete** |
**Context for an assistant answering questions about loops.** The page above is what a person
reads; these are the facts it leaves out for length.
* **Who can:** seeing one loop also needs its **Visible to** audience to include the asker, on
top of the Loops permission. **Run now** needs only view access while Changes is **Never**;
once Changes is **Apply everything**, running it needs edit access, because the run spends the
owner's own write permissions.
* **Limits:** a workspace admits at most 100 loop runs a UTC day, across every loop, trigger and
**Run now**. **Run loop on…** covers all five families a loop can trigger on: a shift, a
timesheet entry, a time-off request, a person or a record; only a document acknowledgement or a
terminal identifier enrolment has no picker. Connectors cover payroll integrations only, and
read their status, not payroll data.
* **Begin AI:** it can file, rewrite, pause or resume a loop from chat, never delete one, and
never touch its capabilities, audience, edit access or owner.
* **Not supported:** there is no level between **Never** and **Apply everything**.
* **Often confused with:** **Workflows**, which reacts to an event with a condition and an action
but never runs Begin AI. A workflow, not a loop, can start from **Loop finished**: a loop's own
trigger list carries no such event.
## Next
Approval mode for an ordinary chat; a loop's own Changes setting works differently.
React to a loop finishing from a workflow of your own.
## Still need help?
Email the Begin team and we'll get back to you.
Open the AI assistant and get instant answers based on these docs.