# pyPerformActionTime recording time in negative value **URL:** \ **Category:** General\ **Tags:** pega-academy\ **Created:** [December 26, 2025, 12:39pm UTC](https://forums.pega.com/t/pyperformactiontime-recording-time-in-negative-value/10439 "2025-12-26T12:39:49Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![ShravyaM16706765](https://avatars.discourse-cdn.com/v4/letter/s/43a26b/32.png) [@ShravyaM16706765](https://forums.pega.com/u/ShravyaM16706765)\ **Post date:** [December 26, 2025, 12:39pm UTC](https://forums.pega.com/t/pyperformactiontime-recording-time-in-negative-value/10439/1 "2025-12-26T12:39:49Z")
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. ---
**Author:** ![RADHAKRISHNA-1](https://avatars.discourse-cdn.com/v4/letter/r/ce7236/32.png) [@RADHAKRISHNA-1](https://forums.pega.com/u/RADHAKRISHNA-1)\ **Post date:** [January 6, 2026, 4:32pm UTC](https://forums.pega.com/t/pyperformactiontime-recording-time-in-negative-value/10439/2 "2026-01-06T16:32:19Z")
hi @ShravyaM16706765 - looks like this property is initialized in NewAssignment DT to 0. This DT is called called by default when a new assignment is created. The value is probably updated in activity performFlowAction.