Failed to create value on component #3 for parameter 'ah_fields'

[JRY]

Hello,

I'm trying to activate my subflow but i'm getting below error don't know what's is exact error. Can someone help me what will be the issue.

"Failed to create value on component #3 for parameter 'ah_fields'"

Thanks,

JRY

[JordanDR]

I'm receiving a similar error after makes changes to my flow designer, specifically after changing some questions in the record producer from which I gather catalog variables. Were you able to find a work around?

[KushalT]

Were you able to find the root cause of this issue @JordanDR ?

[Tara Bauch]

I know it's been awhile since this was first posted, but since I didn't see a solution offered I thought I would share what I just figured out. I was getting a similar issue to this one - except it was saying, "Failure to create value for paramater #6 on 'ah_body'".  It turned out I had some variables that I had changed the name of that didn't get updated in the emails of the flow. Once I removed those older pills and pulled in the updated pills, the situation corrected itself. My guess is that because your error refers to 'ah_fields' that you have some field pills that you pulled into your catalog task that were then changed, so the task is no longer referring to actual fields. Remove those, and then replace with the updated pills and that should work. 

As an aside, I also noticed that the numbers don't always refer to the step that is throwing the error - I ended up having to go through line by line to identify where the mismatched pill names were. 

Hope this helps! 

[William David]

I encountered a similar error, "Failed to create value on component #5 for parameter 'ah_body'" (#5 refers to the Service Now out-of-the-box "Send Email" Action).

It turned out that one (or several) of the "data bubbles" (the 'Community' website won't let me name this properly - weird) inserted in the "Body" input of this Action was/were corrupted by some process (probably due to my modification of the Action that created the "data bubbles", or something similar). I resolved this by deleting all of the "data bubbles", then re-inserting them.