> 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/what-awaiting-service-completion-means-and-how-it-clears.md). # What "Awaiting Service Completion" means and how it clears A recurring service shows "Awaiting Service Completion" when its automation is paused: no new automated outreach or custom tasks will be triggered for that schedule until the service is completed. Scheduling or rescheduling a visit whose visit type covers the service pauses it immediately, without waiting for a background update. It also lands here after outreach or a Custom Task starts the service cycle, while the system waits to confirm the work was done before scheduling the next cycle. It is NOT a task on the Tasks page, so you don't clear it there. It clears when a service completion is recorded. That can happen when the inspection report for the asset group and service is completed, when the Job Summary is submitted for a matching visit with that service's **Create *****service name***** completions on Job Summary submission** switch enabled, or when you edit the recurring service's Last Service Date (you can also edit the Last Date on the asset). When the Job Summary automation matches a group with no assets, Essential clears the status by advancing the recurring schedule from the visit date instead, because there is no asset on which to record a completion. Clocking out alone does not trigger the automation. After a completion is recorded—or the schedule advances directly for an empty group—the schedule resumes, and its next due date and next automation action are recalculated. You can see which recurring services are awaiting completion on the asset group's page. ## Clearing the status by hand If the status is stuck—say the work happened outside Essential and you don't want to record a completion—you can clear it directly. On the asset group's page, find the recurring service in the Recurring Services card and click **Clear** next to "Awaiting Service Completion". The confirmation dialog states when outreach will send or a Custom Task will be created. If the automation cannot run yet, it briefly says why instead. Clearing the status does not record a service completion and does not change any service dates. > **Where to find it:** A recurring-service lifecycle status, not tied to one page: shown on the asset group page (the Recurring Services card and Next Automation status), in the Next Automation Action column on the Asset Groups page, and wherever a property's recurring services surface ## Related guides * [How recurring service automation works (the full cycle)](/administration/how-recurring-service-automation-works-the-full-cycle.md) * [What a service completion is and how it's recorded](/administration/how-recurring-service-automation-works-the-full-cycle/what-a-service-completion-is-and-how-its-recorded.md) * [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 automated outreach batches are built and who they go to](/administration/how-recurring-service-automation-works-the-full-cycle/how-automated-outreach-batches-are-built-and-who-they-go-to.md) * [Visit types: which services an inspection report can complete and reset](/administration/how-recurring-service-automation-works-the-full-cycle/visit-types-which-services-an-inspection-report-can-complete-and-reset.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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://learn.withessential.com/administration/how-recurring-service-automation-works-the-full-cycle/what-awaiting-service-completion-means-and-how-it-clears.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.