> 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/field-operations/assets/setting-up-a-recurring-service-in-depth-frequency-automation-rounding-and-the-asset-filter.md). # Setting up a recurring service in depth: frequency, automation, rounding, and the asset filter Adding a recurring service to an asset group opens a dialog with a handful of settings that together decide when the service comes due and which assets it covers. Service Type picks which service this schedule performs. Occurs Every sets the frequency as a number plus a unit (Day, Week, Month, Quarter, or Year), so 6 Months or 1 Year. Can Trigger Automation? decides whether this schedule feeds your automated outreach: Yes lets it drive automation, No marks the timing as flexible so it tracks a due date but will not kick off automated outreach on its own. Last Service or Installation Date is the anchor the first due date is projected from, and is required when creating a service. Round Due Date can snap the calculated due date to the beginning or the end of the month, or leave it exact, which keeps due dates tidy on monthly or quarterly cadences. The Asset Filter controls scope. With no filter, the service applies to every asset in the group. Add Filter lets you build a condition on asset type and attributes so the schedule applies only to matching assets, and the dialog shows a live count of how many assets currently match. If a group has assets but none match the filter, the service shows **Never Due (no matching Assets)** until a matching asset exists. Editing an existing service saves only what you changed. > **Where to find it:** The Recurring Services card on an asset group; click Add (or Edit on an existing service) to open the Add Recurring Service dialog. ## Related guides * [How recurring service automation works (the full cycle)](/administration/how-recurring-service-automation-works-the-full-cycle.md) * [Recurring service templates and template groups](/field-operations/assets/recurring-service-templates-and-template-groups.md) * [Set up recurring services on an asset group](/field-operations/assets/set-up-recurring-services-on-an-asset-group.md) * [Asset groups and assets: terminology and screen labels](/field-operations/assets/assets-vs-asset-groups-vs-asset-items-the-terminology.md) * [Deleting an asset group (and what it removes)](/field-operations/assets/deleting-an-asset-group-and-what-it-removes.md) * [Manually trigger or delay an asset group's automation](/field-operations/assets/manually-trigger-or-delay-an-asset-groups-automation.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/field-operations/assets/setting-up-a-recurring-service-in-depth-frequency-automation-rounding-and-the-asset-filter.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.