Diagnose issues with shifts

The Operations Control Management Console Logger flags that are available for the FactMES.Server.MaintenanceService assembly can be used to trace the shift change process, including pre‑ and post-shift changes. See Log Flags for Server-Side Diagnostics.

You can also check the last_edit_comment field in shift-related records to see why shift change times did not occur when expected.

• For diagnosing issues with completed shifts, the last_edit_comment field of the corresponding shift_history record contains context information about the shift change, including what conditions were satisfied, the time the shift change took place, and what transaction type (MES or custom) processed the shift change.

  For example:

  MES.Shift.ProcessShiftChangeAsync;ShiftEntId=1;
  ShiftChangedAtUTC=2021-11-09 18:31:00.233;
  Case0:NewShiftStart>CurShiftStart=>UseNewShiftStart.
  NewShiftStart[2021-11-09 18:30:00]>CurrShiftStart[2021-11-09 17:00:00] => EntShiftStart=NewShiftStart;ExclusionEntList=;
  (U):PrevPatternId=0,PrevShiftId=0

  From the example above, the shift change fell into Case 0. The supplied new shift start time is later than the current shift start time on the entity. Therefore, the shift change process is using the supplied new shift start time to change the shift. In this example, the supplied shift start time of 2021‑11‑09 18:30:00 is later than 2021‑11‑09 17:00:00.

• The last_edit_comment field of a shift_to_go record indicates why a change was made to the configured shift. For example, a regular shift that normally starts at 8 am now starts at 10 am after coming back from an overtime shift that ended at 10 am. This would cause the regular shift record's start time to be changed from 8 am to 10 am. The last_edit_comment for the corresponding shift_to_go record contains the information about why the shift start time was adjusted.