function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Kshitij LawateKshitij Lawate 

Understanding timestamp changes for debug logs

We have a trigger on an object which as per the debug logs seems to be taking more than 1.5 seconds to execute. When observed the timestamp in debug logs, there was something unusual. Please find screenshot below. 
The highlighted line indicates completion of code execution for trigger. The time in brackets is in nanoseconds which comes out to be 0.4 seconds. 
But the line, just after that, modifies the timestamp and updates the same by adding 1 second to the time. Any idea, what is the extra processing happening here? 

User-added image