Today I would like to share with you an interesting case that I recently worked on.
Process Portal in BPM 126.96.36.199 showed several completed process instances, all with a certain task in state "new". Clicking the "Run" button for that task did not work. No Task was started, nothing happened. No new window opened, nothing changed.
To further diagnose the problem, we looked at the Process Inspector in the Process Admin Console. Here we saw something pretty amazing:
The instance was marked as completed, and so was the task. At least in the left pane of the Process Inspector. The right frame showed the task as "new". Which is fairly interesting as they contradict each other.
As a next step we had a look at the LSW_TASK table in the BPM database. This showed a status of "11" - which is "new".
So the right hand side and the Process Portal were correct. This task still was in the status "new". So we were facing an inconsistency. As all these bogus instances were listed in Process Portal, our main goal was to get all those tasks completed and get rid of the instances.
Well, I could think of 2 possible options to mark those tasks as completed.
1. Manipulate the database - too risky! Never do that unless IBM Support advised you to and provided clear instructions.
2. Use the REST API - Bingo! As described in the IBM Knowledge Center we can use the REST API to finish tasks. We simply need to use this POST method:
Guess what?! It worked! We simply performed this step for all the tasks that were still marked as "new" and were able to resolve the problem.
However, we were not able to find the cause, why these inconsistent data were present
I hope that one day this may help you solving a problem in your environment. And if it does not, take two of these and call me in the morning.
Your Doctor Debug