"Failed to Create Task"

[samwoo]

Good morning,

We have 3 x Workflows failing to create a Task - this is the error:

Quote

Status : Failed

Last Updated On : 20/09/2024 09:11

Xmlmc method invocation failed for BPM invocation node 's1/task-b2b1792f': <methodCallResult status="fail"> <state> <code>0200</code> <service>task</service> <operation>taskCreate2</operation> <error>Failed to create task</error> </state> </methodCallResult>

I've checked the Task configuration in the Workflows and they all look ok. I've made tweaks in the Workflow Instance, and it's still not working.

Here is the Task Configuration:

1. This Task has worked in previous Workflow Instances with no problem at all using variables, so in these instances, I am hard-coding the values to try and get the ticket to move on
2. I can confirm that the person defined in the user defined in the "User" field is a part of the same team with the ticket, and they have Task Viewing and Assignment
3. I can confirm that the team defined in the "Team" field is a Team that supports the Service
4. For the "Expires After" field, I tried it with the usual variable, with 5 minutes and with no time set

No matter what I do, even taking the Task configuration down to the bare bones, I still get that error.

This is the Outcome configuration and it's only a single button called "Bypass" and the user has to provide a reason to why they are clicking on that button.

I am stumped - that error message doesn't give me anything to go on, and given that the configuration of the Task is now extremely minimal and hard-coded, I am convinced that there is a defect somewhere.

Please can someone look as a matter of urgency.

Thanks,

Samuel

[samwoo]

I've just seen another Failed workflow with this error now... never seen one like this before

Quote

Status : Failed

Last Updated On : 20/09/2024 09:27

Xmlmc method invocation failed for BPM invocation node 's1/flowcode-cc3b61b1': <methodCallResult status="fail"> <state> <code>0200</code> <service>apps</service> <operation>userGetManager</operation> <error>FlowCode Exception (com.hornbill.core/flowcode/fc_bpm/userGetManager): FC2 output error: Schema validation: Restriction violation, enumeration value &apos;managernotfound&apos; not matched (com.hornbill.core/flowcode/fc_bpm/userGetManager/outcome)</error> </state> <diagnostic> <log>2024-09-20 08:27:41.231 [SQL]:[ERROR] MySQL Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near &apos;&apos; at line 6</log> <log>2024-09-20 08:27:41.235 [SYSTEM]:[ERROR] API Request Failed: FlowCode Exception (com.hornbill.core/flowcode/fc_bpm/userGetManager): FC2 output error: Schema validation: Restriction violation, enumeration value &apos;managernotfound&apos; not matched (com.hornbill.core/flowcode/fc_bpm/userGetManager/outcome)</log> </diagnostic> </methodCallResult>

Is there an issue going on?

(ps. The particular workflow gets the manager details of the leaver... the account is archived, but their "Manager" details are still populated - the leaver request was logged after the leaver left hence the reason for the account being archived

edit: I made the user "Active" and tried to refresh this particular workflow, but I am still getting the same error)

[samwoo]

We now have an Incident ticket with this issue appeared moments ago, unrelated to any leavers workflows (which are Service Requests)

[HGrigsby]

 Hi @samwoo

We are also having similar issues with processes that have worked fine for months and now keep failing.

It is affecting our change process and a couple of SRs too. 

 

Helen