---
sourceDocument: Yokohama ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/servicenow-platform

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# State closure in the request fulfillment execution plan

# State closure in the request fulfillment execution plan {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

The state closure in the request fulfillment process of a catalog item depends on the
status of the associated catalog tasks, request items, and the request. It is applicable only
for execution flows.

## State closure dependency between a catalog task and RITM {#state-closure-request__section_xmx_2cc_ydb}

* If all catalog tasks are closed as Closed Complete, the RITM is closed as Closed Complete.
* If there is at least one catalog task closed as Closed Incomplete, the RITM is closed as Closed Incomplete.
* If all catalog tasks are closed as Closed Skipped, the RITM is closed as Closed Skipped.
{#state-closure-request__ul_d3c_gcc_ydb}

## State closure dependency between a RITM and request {#state-closure-request__section_pkl_lcc_ydb}

* If all RITMs are closed as Closed Complete, the request is closed as Closed Complete.
* If there is at least one RITM closed as Closed Incomplete, the request is closed as Closed Incomplete.
* If all RITMs are closed as Closed Skipped, the request is closed as Closed Skipped.
{#state-closure-request__ul_grh_mcc_ydb}