> For the complete documentation index, see [llms.txt](https://docs.3techagency.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3techagency.com/documentation/workflows/tasks-and-schedules.md).

# Tasks and schedules

Run the 8 built-in Task recipes, review proposals, undo a run and schedule recurring jobs.

Tasks run repeatable jobs over many items. Open **WP AI Manager > Playbooks > Tasks and runs**, or select **Automate** on a Playbook. Each execution is a **Task Run** with its status, processed items, proposals, log and, for agent Tasks, a link to its conversation (**Open conversation**).

## Built-in recipes

| Task                           | What it does                                                                                                 | Writes?           |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------ | ----------------- |
| Site health summary            | Read-only review of performance, SEO and content gaps                                                        | No                |
| Draft a blog post from a brief | Reads a recent post for tone, writes a private draft, optional category and stock featured image             | Draft only        |
| Fix missing SEO meta           | Finds pages with no SEO title or description and proposes them                                               | Proposals         |
| Add missing image alt text     | Proposes alt text for Media Library images that have none; attaches the image when the model supports vision | Proposals         |
| Find and replace text          | Replaces a string across pages, including Elementor and other builder content                                | Dry run first     |
| Propose redirects for 404s     | Finds internal links to missing pages and proposes redirects                                                 | Proposals         |
| Put a category on sale         | Sets a sale percentage across a WooCommerce category                                                         | Dry run, approval |
| Back up my site                | Verified database archive; full-site set with UpdraftPlus                                                    | Backup only       |

## Run a Task now

{% stepper %}
{% step %}

### Review the task

Pick it under **Available tasks** and select **Review task**. Check the description, requirements, **Estimate** and inputs. If a requirement is missing, the screen says **Set up the required integration before running this task**.
{% endstep %}

{% step %}

### Choose how changes are applied

**Preview changes first** stages every write as a proposal. **Run automatically** applies permitted changes directly. Large changes still need a verified backup and review.
{% endstep %}

{% step %}

### Run now

Fill in the inputs and select **Run now**. Watch progress in **Run history**. If the page reports a request failure, check Run history before retrying: the run may still be going.
{% endstep %}

{% step %}

### Review and apply

Open the run. Under **Proposed changes**, select rows and choose **Apply selected**. Wait for the list to refresh before selecting more.
{% endstep %}

{% step %}

### Verify or undo

Use **View result** and the links to the changed items. **Undo run** reverses every change that run made.
{% endstep %}
{% endstepper %}

## Safety rules Tasks always follow

* A run that would change **more than 25 items** switches to preview. Applying a selection then needs a verified database backup made **within the last hour**; you are offered **Back up and continue**.
* **Find and replace** always previews first and records one undoable change per page. It scans up to 100 posts by default and at most **500** per run; narrow the scope if you hit the cap. Locked pages and protected pages are skipped.
* **WooCommerce sale and bulk price** changes use a dry run and an approval card.
* Proposals expire after **14 days** without review.
* Task conversations use only the recipe's tools. If you keep chatting in one, it can widen: the assistant can search for other tools, and tools you allow from a card join that chat only. Scheduled runs stay limited to the recipe.

## Schedule a Task

Select **Manage schedule** on a Task that supports scheduling.

| Field                      | Detail                                                                       |
| -------------------------- | ---------------------------------------------------------------------------- |
| Enable schedule            | Turn the schedule on or off without losing it                                |
| Frequency                  | Daily, weekly or monthly                                                     |
| Day of week / Day of month | 0 = Sunday to 6 = Saturday; or 1 to 28                                       |
| Time (site timezone)       | Default 03:00                                                                |
| Scheduled mode             | Writes are **always** staged for review; read-only Tasks finish on their own |
| Max items per run          | Caps the batch size                                                          |
| Notification emails        | Comma-separated; defaults to the site admin email                            |

Select **Save schedule**. The list shows **Next run**. Scheduled runs act as an administrator.

Each run emails a summary with the real counts: proposals waiting, items applied, a review link, the agent's own summary for read-only briefings, and the download link for backups. Home shows **A scheduled task needs your review** until you act.

### When a scheduled run skips

* **Settings > Advanced > Pause all scheduled runs** is on. Schedules are kept; turn it off to resume on the next tick.
* The **monthly token limit** was reached. Chat still works; schedules stand down with a logged reason.
* The license is not active, or a required integration went missing.
* The site has no Action Scheduler and gets little traffic, so WP-Cron fires late. Set a server cron to call `wp-cron.php` every 5 minutes.

See [A Task did not change the site](https://docs.3techagency.com/help-center/workflows-and-recovery/task-did-not-change-the-site) in the Help Center.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.3techagency.com/documentation/workflows/tasks-and-schedules.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.