The Plug-in Trace Log stores timestamps such as PerformanceExecutionStartTime as datetime fields, but milliseconds is always 0.
To be able to make correct analysis of execution sequences, these fields need to include milliseconds, as it is now impossible to know in which order plugins were actually executed.
This has been completed/now possible and the PM, Jim will give a more complete answer but until please see the documentation:
I am completely lost as to why this is not already there. Such a simple addition but has a huge impact on tracing issues.
Same concept applies not just to plugins, but to all workflow executions. Even without plugins, when multiple workflows are registered, determining order of operations in which they are fired is somewhat important. Just a tiny bit 😉
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.