Question
posted transaction id for frame 'pyWorkPage' DOES NOT match record in Pega 8.4
Hello All,
I can see some hot fixes/ articles for earlier versions. we are having same issue exists in 8.4.4 and didn't see any information recently, what will be the fix for this issue. Please suggest.
Thank you,
Vijay
Accepted Solution
Updated: 29 Mar 2022 8:03 EDT
Pegasystems Inc.
GB
@vijayt63 the error you are reporting is not a specific issue that was rectified with hotfixes. Often these issues occur due to a configuration problem in the operating environment - for example On Submit button action, there is an additional ReloadSection firing along with FinishAssignment which is using old pztransactionID.
The way to actually debug a stale transaction error is to gather a Fiddler trace and analyze that, along with the error message from the PegaRULES log file that coincides with the time the Fiddler log was gathered.
Can you please collect such a Fiddler log for the steps that generate the error? Also check the actual error from the PegaRules log file. With these two, our support department should be able to identify the root cause of the issue.
If you're not familiar with Fiddler, it can be downloaded from here: https://www.telerik.com/download/fiddler
Please run a fiddler trace to capture good and bad id's and identify where the commit is being performed. If it's a commit in custom code that is not needed, try removing it.
Anthem
US
Hello Moderators,
We are facing the same issue.
I would appreciate if you can find the right point of contact from Pega to look into this matter.
Accepted Solution
Updated: 29 Mar 2022 8:03 EDT
Pegasystems Inc.
GB
@vijayt63 the error you are reporting is not a specific issue that was rectified with hotfixes. Often these issues occur due to a configuration problem in the operating environment - for example On Submit button action, there is an additional ReloadSection firing along with FinishAssignment which is using old pztransactionID.
The way to actually debug a stale transaction error is to gather a Fiddler trace and analyze that, along with the error message from the PegaRULES log file that coincides with the time the Fiddler log was gathered.
Can you please collect such a Fiddler log for the steps that generate the error? Also check the actual error from the PegaRules log file. With these two, our support department should be able to identify the root cause of the issue.
If you're not familiar with Fiddler, it can be downloaded from here: https://www.telerik.com/download/fiddler
Please run a fiddler trace to capture good and bad id's and identify where the commit is being performed. If it's a commit in custom code that is not needed, try removing it.
Great American Insurance Company
US
@MarijeSchillern Thank you! The same issue is happening again after we upgraded to 8.4, but only for 1-2 instance daily and we are not able to replicate the scenario, populating with error message - "The action is not allowed as it is outside the current transaction". We can see this message in logs - "posted transaction id 'XXXXXXX...' for frame 'pyWorkPage' DOES NOT match record 'XXXXXX...".
Please suggest or direct to Pega contact to look in to this issue
Thank you,
Vijay
Updated: 27 Jun 2022 9:02 EDT
Pegasystems Inc.
GB
@vijayt63 our support document Troubleshooting stale work, validation errors, and work processing failures caused by Transaction ID mismatch should help you analyze your issue in-depth.
Please can you log a support incident for the instance you have encountered, as suggested previously?