Skip to main content
10-Marble
Nov 18, 2026 6:54 PM UTC
Question

How to retain entries in a Processing Queue until a scheduled job processes them?

Hi all,

I’m looking for some guidance on a Windchill queue design.

As part of a requirement, we are using a Processing Queue to capture document release events. When a document is released, an event listener creates a queue entry containing information such as the document OID.

The intent is for the queue to continue accumulating these entries as documents are released throughout the day. A separate scheduled job would then run at a configured time, read the accumulated queue entries, and perform further processing for each document.

The issue is that entries added to the Processing Queue are executed immediately, so by the time the scheduled job runs, there are no entries remaining in the queue. I understand that this is the default behavior of Windchill Processing/Pool Queues.

Has anyone implemented a similar pattern where:

  1. Queue entries are added throughout the day but remain pending without being executed.
  2. A scheduled job later retrieves and processes those entries.
  3. The schedule can be changed independently without affecting how the events are captured.

Is there a supported way to configure a Processing/Pool Queue so that entries remain in the queue until explicitly processed? Or is there another Windchill queue mechanism/design pattern that would be more appropriate for this requirement?

The reason for keeping the scheduler separate is to provide flexibility in changing the processing schedule based on business requirements.

Thanks in advance for any guidance or examples.

Regards,
Ismail