> 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/help-center/workflows-and-recovery/task-did-not-change-the-site.md).

# A Task did not change the site

Check proposals, expiry, run status and schedule skips.

Open **WP AI Manager > Playbooks > Tasks and runs**, then the run in **Run history**.

**It finished with proposals.** That is preview working as intended. Select the rows under **Proposed changes** and choose **Apply selected**. Wait for the list to refresh before selecting more.

**Apply is refused.** Either the proposals are older than **14 days** and expired, or the run touches more than 25 items and needs a verified database backup from the last hour. Use **Back up and continue**.

**A scheduled run skipped or never ran.** Check:

* **Settings > Advanced > Pause all scheduled runs**
* the **Monthly token limit** (scheduled runs stand down past it)
* the license state
* a missing integration on the Task
* WP-Cron on a quiet site without Action Scheduler: set a server cron to call `wp-cron.php` every 5 minutes

Scheduled writes are always staged for review, even if the Task is set to run automatically. Read-only Tasks finish on their own.

**Find and replace missed pages.** It scans up to 100 posts by default and at most 500 per run. Narrow the scope or run it again. Locked and protected pages are skipped.

**WooCommerce prices did not change.** Bulk price and sale changes wait for approval after the dry run.

A chat reply alone never proves a Task wrote anything. See [Tasks and schedules](https://docs.3techagency.com/documentation/workflows/tasks-and-schedules).


---

# 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/help-center/workflows-and-recovery/task-did-not-change-the-site.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.