Error Reference

Requested item stuck in open state: fulfillment not progressing

Requested item stuck in open state: fulfillment not progressing

Where this appears

This error typically appears in the Requested Item (RITM) record when monitoring catalog fulfillment progress or in system notifications. The error indicates that a catalog item request has remained in the Open state without advancing to Work in Progress or other expected states. ServiceNow administrators may also see this in workflow diagnostics or catalog management reports.

Sourdough
Chrome Extension

Debugging this in a real instance?

Sourdough lets you trace "Requested item stuck in open state: fulfillment not progressing" through system logs, script errors, and API health in the ServiceNow tab you are already using.

Add to Chrome

Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.

Overview
Tasks
CMDB
API
Metrics
Monitor
Internals
Instance:sourdoughdev·Version:Yokohama
Instance StateONLINE
System StatusFully Operational
Session Timeout90 minutes
Logged-In Sessions2 (20 active)
Build Nameyokohama-12-18-2024_p1
IP Address10.159.128.43
Instance HealthHealth Score: 90%
🔥 5dSourdough (Chrome Plugin)Dark Mode

Cause

The associated workflow or flow is stuck or has failed, preventing the RITM from transitioning to the next state in the fulfillment process. (high likelihood)

The RITM was not properly assigned to a fulfillment group or the assigned group was not notified due to notification configuration issues. (high likelihood)

A required approval is pending or stuck, blocking the RITM from progressing to the fulfillment stage. (medium likelihood)

Business rules or script includes are preventing the RITM state transition due to validation failures or script errors. (medium likelihood)

The catalog item configuration is missing required workflow assignments or has incorrect stage definitions. (low likelihood)

Fix

Step 1: Navigate to the RITM record and check the Related Links section for any active workflows or flows, then verify their current execution status.

Step 2: Review the System Log at System Diagnostics > Log > Application Log for any workflow execution errors or script failures related to the RITM number.

Step 3: Check the RITM's Assignment group field and verify that the assigned group exists, is active, and has members with appropriate roles to fulfill the request.

Step 4: Navigate to Workflow > Workflow Admin > Running Processes to locate the workflow instance and examine any error states or waiting activities.

Step 5: Review the Approvals related list on the RITM record to identify any pending or stuck approvals that may be blocking progression.

Step 6: Examine the catalog item configuration under Service Catalog > Catalog Definitions > Maintain Items to ensure the workflow is properly associated and configured.

Step 7: If workflow is stuck, either restart the workflow activity from the Workflow Admin console or manually advance the RITM state after resolving underlying issues.

Step 8: Test the catalog item fulfillment process in a sub-production environment to verify the fix and ensure proper state transitions.

Test Your Knowledge

Quick 3-question quiz. See how your ServiceNow skills stack up.

Question 1 of 3Performance

A list view on a table with millions of records is slow. Best fix?

Select an answer to continue