Jira Spoke erroring when using Create Issue action?

[Kiran_25]

I am facing a "Could not deserialize value from sys_flow_value sys_id" error when using the Jira Spoke Create Issue action in a flow.

I have been able to see that the error is due to the ptask number not being passed but it is populated in the flow.

The sys_flow_log errors show:
"errorMessage:Error: PTask Number: PTask Number is required. (Process Automation.5e66797e9f9c02105760e6073b0a1c1c; line 3), errorCode:1".


Previously when testing this error was not occuring. No changes have been made to the flow or on jira side that would break this

[pavani_paluri]

HI @Kiran_25 ,

I’d start by checking what the Create Issue action is actually receiving at runtime. The error suggests the action isn't getting a valid value for PTask Number, even though the data pill looks populated in Flow Designer.

I've seen cases where a pill displays a value, but resolves to null or an unexpected object when the flow executes, which can trigger the "Could not deserialize value from sys_flow_value sys_id" error.

As a quick test, try hardcoding a valid PTask number in the Create Issue action. If that works, the issue is likely with the data pill mapping rather than Jira itself.Also check the Flow Execution Details and inspect the inputs passed to the Jira action. I'd be interested to see whether the action is receiving the actual PTask number or a record/sys_id reference instead.

Since you mentioned this was working previously and nothing has changed in the flow, it's also worth checking whether there were any recent platform or Jira Spoke updates that could have affected input validation.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for

Kind Regards,

Pavani P

[Kiran_25]

Hi @pavani_paluri I am unable to open the execution details and I see the 'could not deserialize' error when I try to open. 

IN the outbound http logs the POST is showing a 400 error code occured.

I have tried removing the data pill and hardcoding the value but the same issue occurs. In the flow enginge context logs the error logs are showing:
"error: PTask Number: PTask Number is required. (Process Automation.5e66797e9f9c02105760e6073b0a1c1c; line 3):"