Support Article

TransactionID error message in logs when used in IE browser



TransactionID errors continually appear in the log file. The user does not notice any error on the screen.

Error Messages

1) ( mgmt.base.ThreadUITransaction) ERROR - ERROR: posted transaction id '4d5388eb22b51c2effe646db8e975032' for frame 'pyWorkPage' DOES NOT match record 'bcc771b5e157c45b5e56ed907963d38a'

2) (ngineinterface.service.HttpAPI) : java.lang.NullPointerException

Steps to Reproduce

The first error is reproducible when a new CPM Interaction Phone call is launched and went to the Interaction driver.

The first and second errors are reproducible when the user tries to end the call and the CPMPortalRecent activity is executed.

Root Cause

An issue in the custom application code or rules.

The response to a single user action, if it results in multiple requests being sent to the server, may result in a commit on the server.

For these use cases, FinishAssignment is firing. This changes the pzTransactionID, rendering void any subsequent POST requests which use the previous (and now stale) pzTransactionID.

For both of these use cases, user can see that other POST requests are firing near simultaneously with the FinishAssignment.

As a result, the requests which fire after the FinishAssignment are using a stale pzTransactionID and fail.


Perform the following local-change:

Modify the requests that occur on these user actions so that the FinishAssignment fires last, and that there is no possibility of a race condition with a previous action that might be using the same pzTransactionID as the FinishAssignment.

Published April 5, 2017 - Updated April 26, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.