Skip to main content
rands4-Participant
4-Participant
Oct 14, 2026 2:48 PM UTC
Question

Windchill Publish Delayed

I am using Windchill PDMLink Release 12.0 and Datecode with CPS 12.0.2.26 Recently in our test environment we have identified that APE publishes wait until 9:58pm to start the publish. The worker is set to auto start and does not have an 'available time' set which I believe would mean it should always be available. I have been unable to identify a setting or configuration that would force Windchill to hold the publish till a set time to then send to PE. From the WVS Job Monitor: Job Submitted: 2026-10-13 15:23 EDT Job Start: 2026-10-13 21:58 EDT Job End: Job Submitted: 2026-10-09 16:35 EDT Job Start: 2026-10-09 21:58 EDT Job End: 2026-10-10 12:36 EDT Job Submitted: 2026-10-08 10:44 EDT Job Start: 2026-10-08 21:58 EDT Job End: 2026-10-09 09:05 EDT Job Submitted: 2026-10-06 16:03 EDT Job Start: 2026-10-06 21:58 EDT Job End: 2026-10-07 11:19 EDT Job Submitted: 2026-10-05 16:42 EDT Job Start: 2026-10-05 21:58 EDT Job End: 2026-10-06 13:31 EDT As shown above independent of the job submitted time the job start time is 21:58 each time. Any assistance that can be provided with this would be greatly appreciated.

4 replies

TDT18-Opal
18-Opal
Oct 15, 2026 5:32 AM UTC

Were a large number of jobs already in the Ready state? If not, have you checked whether the Priority Queue is in the Started state?
Is this issue occurring for all jobs?

Translate
rands4-ParticipantAuthor
4-Participant
Oct 19, 2026 12:37 PM UTC

Sorry for the delay, thought I would get an email when replies were left. This happens whether other items are in the queue or not. Upon further investigation it appears to be related in some way to the worker restarting at 9:58pm (I believe this happens daily as it had initially started at 9:58pm and restarts after 24 hours). Due to this I have set the autobusytime to 5 minutes to force the worker to restart after 5 minutes of running (after finishing its current publish) to see if the worker starting fresh before each publish may resolve this issue. So far this does seem to have resolved the submitted and started time being different, but how much overhead I’m adding to the system in restarting the worker each time I’m not really sure.

Translate
X-FLS
X-FLS6-Contributor
Oct 15, 2026 9:24 AM UTC

Check for publish.publishqueue.availabletimes in wvs.properties.
This queue-level window is separate from the worker’s agent.ini availabletime and would hold jobs until it opens.

Translate
rands4-ParticipantAuthor
4-Participant
Oct 19, 2026 12:38 PM UTC

Sorry for the delay in replying! There isn’t currently a setting by that name in the wvs.properties file. 

Translate
Terms & ConditionsAccessibility statement