We have observed that in our audit history, over 10,000 records in the last two years have pyPerformActionTime set to -2147483648. This property is intended to represent the number of seconds a user spent locked to the case while performing an action, so it should never be negative.

Observations:

• Occurs only for Local Actions (not for assignment/flow actions).
• The value -2147483648 equals Integer is recording  in data 

• Challanges:
  Unable to trace this issue in production due to limitations. Need suggestions on:

• How to debug or trace effectively in a non-production environment to identify the exact rule or logic writing pyPerformActionTime.
• Which OOTB rules or activities handle this property for local actions.