Question
PayPal
IN
Last activity: 31 Aug 2018 14:01 EDT
ERROR: posted transaction id 'xxx' for frame 'pyWorkPage' DOES NOT match record 'yyy'
Following exceptions are observed in logs often.
ERROR: posted transaction id 'xxx' for frame 'pyWorkPage' DOES NOT match record 'yyy'
We are able to replicate the scenario in which the logs can be printed . As i had seen in other PDN posts, pztransactionid change during commit was explained to be the reason for this error. Could anyone let me know how we can trace the pztransactionid while replicating?
***Edited by Moderator Marissa to update platform capability tags****
Pegasystems Inc.
FR
Hello,
Fiddler would be your best option to trace pzTransactionId. But you don't need to use it. You can just replicate your behavior and check where the manual Commit has been triggered.
PayPal
IN
Hi, Thanks for the reply.
In fiddler, changed transaction id 'yyy'(in dis case) is not available. Hence it is difficult to find the exact transaction at which transaction id got changed.Could you please elaborate how pztransactionid can be traced through fiddler?
Also, Only commit present on the tracer was Work- WorkCommit called as part of the Finish assignment step.There are no other manual commits.
Pegasystems Inc.
FR
Yes this commit will be sufficient to generate this transaction id issue. I guess you are coming from a custom configuration with a FlowAction calling a LocalAction or the other way around.
PayPal
IN
Thank you.
Yes. It is occuring part of a flow action.
Finish assignment is being called in the action set of a button.
So on click of that button, Finish assignment will be called and then the flow will move on to the next assignment(screen).On this scenario ,transaction id error happens. Any approach for mitigating this?