Skip to main content
Solved

Task allocation/committed before shift time of resource in POS

  • June 10, 2026
  • 3 replies
  • 29 views
D
Sidekick (Partner)
Forum|alt.badge.img+7

Hi All,

Facing an issue with allocation/commitment,  activity was committed  at 4  AM but resource shift will start 08AM  and end at 4 PM for entire week  but how activity  got allocated at early Moring before shift time .  

ex: SLA of the activity was 09/09/2026-11:54 PM  end  SLA- 06/10/2026-12 PM when i see in PSO task was committed at 4 AM today (06/10/26) actually  without shift timings PSO should not allocate and commit but how this was  committed? we  defined commit rules and  Time Before Shift Start  to 4 hrs. 
will  pso allow to commit task  before shift time  due to  time before shift value?

 can please suggest how we can stop allocation/commitment before shift time?
 

 

Best answer by WESALK

Hi Durga,

PSO does not commit activities directly. It only generates commit suggestions based on the configured commit rules, while the actual commit acknowledgment is sent by FSM confirming the commit. 

Could you please share the commit suggestion message generated by the PSO DSP service for this task? It should be available in the PSO audit logs around the 4:00 AM timestamp, in a PLAN CHANGE file under the "Suggested Dispatch" entity.

This information will help determine whether the issue originated in PSO's suggestion logic or during FSM's commit processing.

    3 replies

    W
    Do Gooder (Partner)
    Forum|alt.badge.img+1
    • WESALK
    • Do Gooder (Partner)
    • June 10, 2026

    Based on the screenshot, the task appears to be fixed to both a specific resource and a specific date/time (10 June at 4:00 AM). This suggests that the scheduling was likely applied manually by a user through the Workbench, or that an update was sent from the integration to PSO with instructions to schedule the task at that exact time.

    I guess it is better reviewing any configurations, business processes, or scheduling rules in the external application that could result in activities being fixed in this manner. Because PSO inherently would not schedule activities in this manner (unless it's a defect).

    Additionally, review the activity history for the affected order ID. If the Reason field contains a username, the update was most likely performed manually by a dispatcher or user, Else the date_time_fixed status was likely generated by the integration/external application logic, and that logic should be investigated further.

      D
      Sidekick (Partner)
      Forum|alt.badge.img+7
      • Durga
      • Author
      • Sidekick (Partner)
      • June 10, 2026

      Hi ​@WESALK ,

      Thanks for the response!! 

       Task was  committed by PSO  first,  once PSO committed data will sync  after person id  and status updated  in FSM there was a business rule will update fixed person as ‘Y’ from fsm. not only one task we have observer many task which sla start from 10 pm - end day next date 12 pm , orders  have same pattern all are committed by PSO around 4 :00 AM  onwards.

       added one more example here: task  sla was 8”00- am 1:00 PM if we see in below screen shot task was committed at 4 AM  once time committed  automatically plan start and end also will update accordingly. 

       there is no manual  allocation from both and fsm and pso why pso  committed that time automatically  since there is no shifts? 

       

      Thanks,

      Durga

      W
      Do Gooder (Partner)
      Forum|alt.badge.img+1
      • WESALK
      • Do Gooder (Partner)
      • Answer
      • June 10, 2026

      Hi Durga,

      PSO does not commit activities directly. It only generates commit suggestions based on the configured commit rules, while the actual commit acknowledgment is sent by FSM confirming the commit. 

      Could you please share the commit suggestion message generated by the PSO DSP service for this task? It should be available in the PSO audit logs around the 4:00 AM timestamp, in a PLAN CHANGE file under the "Suggested Dispatch" entity.

      This information will help determine whether the issue originated in PSO's suggestion logic or during FSM's commit processing.

      Terms & ConditionsAccessibility statement