You might have noticed an Ultimus Error The status of this task is 1 It cannot be submitted, While you are submitting a task from your inbox. This error occurs on the line of code where you use SendTask method. Actually the message is somewhat irrelevant to the error which is occurring at the back-end and it might have following reasons.
1. Invalid Step Recipient: You have not set the step recipient as
- A valid short name of the person
- The organizational chart group is invalid
- Job function group is invalid
- The dynamic recipient string used to set dynamic recipient is incorrect e.g. USER:org=Business Organization,user=UserShortName has some invalid values or syntax.
Solution to this problem is that you have to carefully check all the step recipients and their assignments.
2. Another scenario which I came across today is that you have 2 BPM servers with NLB (Network Load Balancing Configuration) and you are using email connectors to send emails via email flobots in the process maps. But one of the server’s BPM studio doesn’t have email connectors on it, and mistakenly you used the server with email connectors to publish the process on the server. But when the end user accessed the process through inbox task and tried to submit and the request went to other server which doesn’t have the email connectors. So it failed and generated an error while sending the task ‘The status of this task is 1 It cannot be submitted’.
Solution to this problem is to create the email connector on the other server and publish the process again on the faulty server. Although both servers are pointing to same DB repository but its strange that the email connectors on both BPM servers are stored differently.
3. Another reason this error comes up is that if you try to abort a step via step rules or code, and the step being aborted is not active, your send task method will generate the error ‘The status of this task is 1 It cannot be submitted’.
Solution to this problem is that you have to modify the step rules/code and add one more condition to check if the step status is active then abort the step. It will be fixed.
4. Yet another reason for this error could be that there is a known issue with the junction step. Sometimes junction step doesn’t go into delay or sometimes it doesn’t come out of delay. Sometimes if you have modified junction step rules to abort it, you may get this error so you have to delete the junction step, create it again, place the rules again and then publish. It will work.
So its really hard to catch this error and resolve it.