Skip to main content

Our org is very basic in that we only use task bots. We do not have AARI, AI, or any of the other components used in this training camp.

Thus, a large hurdle in this camp so far is just getting used to Process Composer, API tasks, etc.

I am having an issue where the JSON output from the AI Skill cant be parsed by the API task that retrieves it. But debugging this issue seems tricky since, unlike a regular task bot, I can’t just debug it or use a message box or even log it to a .txt to figure out what’s wrong.

So, I am curious what everyone else here is doing to debug their process flows?

Hey ​@LoganPrice,

When it comes to debugging API Tasks, you have 2 options.

1, You are able to use the Debug mode to monitor variable values as it executes.

2. As a developer, you can build what is in an API task into a Task Bot. Here you can execute as normal to ensure everything is working, and then transfer the logic back into an API Task. 


Feel free to send me a message if you want assistance troubleshooting.

If you are having issues with parsing the JSON output from the Ai Skill “Summarize,” it is most likely due to a hidden character that is in the prompt.  This most likely happened when copying and pasting from Word into the prompt.  To fix, remove the spaces before the word “summary” in the prompt:

 

 

In the process you do have task bots or can add task bots with message box statements to see what values are going to and from parts of the process.

Reply


Terms & ConditionsCookie settings