> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/how-recurring-service-automation-works-the-full-cycle/why-isnt-an-asset-groups-automation-running-blockers.md).

# Why isn't an asset group's automation running? (blockers)

When an asset group's automation can't proceed, the Next Automation card shows no next step. In its place it reads "No next automation," followed by the reason or reasons, joined into a single gray line. The reasons fall into two kinds.

Setup problems to fix: "no contact to send to" (Automated Outreach needs a contact to send to, so add a contact role on the property), "customer is inactive", "property is inactive", and "asset group is inactive" (reactivate whichever applies).

Expected, temporary states, not errors: "awaiting service completion" (the schedule is paused until the current service is completed) and "set to not trigger automation" (the recurring service uses flexible timing, so it never fires automatically and you schedule it yourself).

Fixing a setup problem lets the automation resume; the temporary ones clear on their own as the work gets done. The missing-contact reason also surfaces as a colored pill ("Add a contact role to this property to enable outreach") inside the Edit Automation modal when you open it for an outreach service with no contact role.

On a property's Asset Groups list, "No Next Automation Scheduled" means automation is enabled but no next action is available. Open the asset group and check its Next Automation card for a reason. "No Automation Set" means none of the group's recurring services has automation enabled.

If creating a group shows "Asset group saved, but automation setup failed," the group is already saved. Don't create it again. Contact support to restore its next automation.

> **Where to find it:** On the asset group page, the Next Automation card shows the reasons as a single gray "No next automation, ..." line in place of a next step

## Related guides

* [Custom Task automation: an internal task instead of customer outreach](/administration/how-recurring-service-automation-works-the-full-cycle/custom-task-automation-an-internal-task-instead-of-customer-outreach.md)
* [How recurring service automation works (the full cycle)](/administration/how-recurring-service-automation-works-the-full-cycle.md)
* [What "Awaiting Service Completion" means and how it clears](/administration/how-recurring-service-automation-works-the-full-cycle/what-awaiting-service-completion-means-and-how-it-clears.md)
* [What automated outreach sends, and previewing it](/administration/how-recurring-service-automation-works-the-full-cycle/what-automated-outreach-sends-and-previewing-it.md)
* [Custom fields: your business's extra fields on records](/administration/basics/custom-fields-your-businesss-extra-fields-on-records.md)


---

# 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://learn.withessential.com/administration/how-recurring-service-automation-works-the-full-cycle/why-isnt-an-asset-groups-automation-running-blockers.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.