As you can tell, in the good package, the last two curly brackets are there, in the bad one, the message is truncated and stops too early. Not sure why. From Postman I can send the message correctly and every json validator I have checked says it is a good json string. The main thing I also noticed, is that when the job runs, under the logs for the job, there is a new tab, Run Info. Under this tab there is a Request body field. The Web Service field has the two curly brackets there, but under this tab, the Run Info tab, they are missing. I am guessing that somewhere between parsing and send the message, Tidal drops the last two curly brackets.
To participate in this event, please use the button to ask your questions
This special event - formerly known as Ask the Expert- is open only to Cisco Customers and Partners.
Many pages in the Cisco Community are acce...
About this webinar
Cisco Application Centric Infrastructure (ACI) is designed API first, making it an automator’s, developer’s and programmer’s dream. When every aspect of a product is available via an API, there is no limit to the scale, robustnes...
Community Live - Application Centric Infrastructure: Introduction and Configuration Best Practices
This special event - formerly known as webcast- is open only to Cisco Customers and Partners.
Many pages in the Cisco Community are accessible o...