> This page is for Itential Platform On-Prem, version 6 (default).
> For other versions, use one of these documentation indexes:
> - 6 (default): https://docs.itential.com/itential-platform/6/llms.txt
> - 2023.2: https://docs.itential.com/itential-platform/2023-2/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.itential.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server.

# Service Requests terms and concepts

> Learn the key terms, the triggers that become services, and the status definitions used in Service Requests.

## Key terms

**Request**

A record that you asked Service Requests to carry out a service. You submit a request, or a schedule submits it at each scheduled time. Each request has a status that you can track.

**Run**

The execution that a request starts, such as a workflow job or an agent session. The status of a request reflects the status of its run.

**Schedule**

A durable definition that requests a service repeatedly. One service can have many schedules.

**Service**

A manual trigger that you can request from Service Requests. A service starts an agent or a workflow, and Service Requests presents both the same way.

## Status definitions

Each request has one status. The status reflects the run that the request started, such as a workflow job, a Lifecycle Manager action, a Configuration Manager compliance plan, or an agent session.

* **In progress**: The run is in progress. Paused and pending runs also show In progress.
* **Error**: The request stopped because of an error that you can't fix. If an administrator fixes the cause, the request can return to In progress.
* **Complete**: The run finished.
* **Canceled**: The request was stopped before its run finished.

> **Warning**
>
> Complete means that the run finished, not that the request succeeded. A completed request can include handled task errors, failed devices, or a failed agent. To check the outcome, open the request and review its output.

## Schedule states

* **Scheduled**: The schedule is enabled and requests the service at the next scheduled time.
* **Paused**: The schedule is disabled and doesn't request the service until you enable it.

If the trigger for the service is disabled, the schedule's toggle is switched off and locked, and the schedule doesn't request the service. You can't enable the schedule until the trigger is enabled again. The schedule then returns to its previous setting.