App failing with transaction id mismatch error
SummaryTransaction id mismatch errors are occurring and stopping the application from running.
In the Pega log:posted transaction id 'e98bd46a75fb8b50dbb8f5f1130a1337' for frame 'pyWorkPage' DOES NOT match record '722b2539d82311e2e1ab56c4e6cdbf5d'
In the Fiddler file (may not be visible on application user screen):
This action is not allowed as it is outside the current transaction
Steps to Reproduce
- In Designer Studio, include a button with multiple actions, such that one that is NOT the last causes a commit. For instance, the "FinishAssignment" action.
- Run the application and click the button.
- Observe that if the commit occurs, the subsequent actions associated with that button encounter the transaction id mismatch error.
Root CauseA flow action contains a commit, which causes the transaction id to change. This causes the subsequent action to fail with the previous transaction id.
ResolutionRemove the actions containing the commit. If the action can not be removed, re-order the actions so the commit is performed after the transaction ID is assigned.
Published February 3, 2017 - Updated February 10, 2017