@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.
@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
Posted: 3 months ago
Updated: 3 months ago
Posted: 27 Jun 2022 9:01 EDT Updated: 27 Jun 2022 9:02 EDT
Marije Schillern (MarijeSchillern)
Senior Knowledge Management Specialist