How to identify this issue
This issue can show up on QAWeb Server as an 'Internal issue'. Read more about internal issues in the linked knowledge base article: [KB7878].
When you click on 'View issue' next to the internal issue in the 'Issues and Actions: In progress' overview, you will see an issue detail on the next page. In this case, it looks like the following screenshot:
This can happen with any kind of test, not just the 'Mammo Compliance Test' like in this example.
Root cause
As this is a very rare issue, we have never been able to identify the root cause. We do, however, assume that this is caused by one or more locked tables in the QAWeb Server database while we attempt to write this action result in the database.
Solution
The solution is very easy: Retry the action and the issue will be solved:
- Click [Retry or close]
- Choose the following option:
- Click [Next >>]
- Wait for the action to disappear from the 'Issues and Actions: In Progress' list.
