@tomgreenwood @Sajith Anushan 

Can you post a screenshot? What version of PSO are you running?

What upstream system did you use - FSM/IFS Cloud/other system? When you send a LOAD message, you define the scheduling horizon (“duration”) and this does not change over time. So if you send a LOAD message with duration=5 and CHANGE messages during the next 6 days, you may see that the red line passes the blue line.

Just guessing though...

@Alexander Heinze Thanks Sir.The PSO version is 6.10.0.12

The screenshot u have shared is exactly the issue I am facing as a result the tasks in queue are getting unallocated.

Yes it is FSM which is upstream source.

Please suggest me how can I avoid this.

@anmise  thanks Sir.The PSO version is 6.10.0.12

I believe you need to setup a timeline refresh message in monitor schedules (at least that’s how it worked before, it’s been a long time since I used it). 

Send an XML like this every 1-5 minutes or so, as an explicit call. 

<perform_batch>
<perform_advance_threesixty_time>
  <parameters>
    <dataset_id>YOUR_DATASET_ID</dataset_id>
  </parameters>
</perform_advance_threesixty_time>
</perform_batch>

I think Alex’s suggestion is most likely here, if you aren’t sending a load each day the current time (sent on the change files) will eventually exceed the end of the scheduling window

@tomgreenwood @Alexander Heinze Thank u Sir.The advance time schedule process was running for me every 5 mins still I have faced the issue.

Hi Shamik,

Yes, as I said the issue is most probably that you are not sending a load each morning. If you don’t do this the scheduling end date isn’t updated.

Regards,

Tom

Yes, the time line update does not move the Scheduling window. You need to send a daily load.