We are experiencing some issues with status synchronization between PSO and FSM.

ISSUE 1 and 2: TASK CREATION with or without fixed_commitment

1. An activity is created (XML), with or without fixed_commitment flag;
2. In FSM, the task status is Open;
3. PSO automatically allocates the activity;
4. In FSM, the task status changes to Unassigned (with fixed_commitment) or remains Open (without fixed_commitment);
   1. In FSM, the schedule_status in the TASK table is 0.
   2. In FSM, the update in the DSE_ALLOCATION table takes a while (sometimes minutes, sometimes hours);
5. The activity is manually committed in PSO;
6. In FSM, the task status remains Unassigned (with fixed_commitment) or changes to Unassigned (without fixed_commitment);
   1. In FSM, the schedule_status in the TASK table is still 0.
7. After some minutes, the activity in PSO automatically reverts to Allocated (overriding the manual Committed status).

TASK CREATION and FIXED_RESOURCE IN PSO

If the resource is fixed in PSO (fixed_resource), the behaviour changes as follows:

1. An activity is created (XML);
2. In FSM, the task status is Open;
3. PSO automatically allocates the activity, but tis time it is fixed to a resource;
4. In FSM, the task status changes to Unassigned;
   1. In FSM, the schedule_status in the TASK table is 0.
   2. In FSM, the update in the DSE_ALLOCATION table takes a while (sometimes minutes, sometimes hours);
5. The activity is manually committed in PSO;
6. In FSM, the task status changes to Commited;
   1. In FSM, the schedule_status in the TASK table updates to 30;
7. The activity remains committed in PSO.

We do not understant why this status synchronization only occurs when the activity is fixed to a resource in PSO. In all other cases, the task status and schedule_status do not update, and PSO reverts the activity status from Committed to Allocated.

In both cases, the broadcast in Scheduling Output History is sent with the updates taken by PSO to FSM.