Chad_Maggard | 2019-05-31 19:55:23 UTC | #1
Using Architect or building the action within Purecloud produces success rate of 50 percent or less. We are using a IIS server hosted on AWS. We receive the error " 10. Validate output against schema: JSON failed schema validation for the following reasons: instance type (object) does not match any allowed primitive type (allowed: ["array"])"
Then, not change anything,, and rerun the test .. and we will get a success. Architect is taking the failure path and not the timeout path.
IIS logs show that results are null coming back from AWS.
Jason_Mathison | 2019-06-03 17:21:22 UTC | #2
Hi Chad,
Just to see if I understand, when you said that "IIS logs show that results are null coming back from AWS." Do you mean that the results are always coming back as null, or only when your action fails?
In general, I would probably hit the webservice with a tool like postman or curl and see if you are consistently getting the same results back. If you can verify that your web service is always sending back the same (or correct) results but the data action is sometimes working and sometimes failing then please open up a case with customer care to troubleshoot.
--Jason
Chad_Maggard | 2019-06-04 13:47:32 UTC | #3
The results come back as null within the IIS logs only when the action fails Postman never fails. We do have a support ticket open.
tim.smith | 2019-06-04 14:10:57 UTC | #4
Please continue to work with Care. The dev forum is not a way to bypass Care.
Jason_Mathison | 2019-06-04 14:26:59 UTC | #5
The only suggestion I have left is to see if the data action is sometimes sending problematic input to your web service. You could do that by logging out the inputs to your web service in the IIS logs or by having the IVR speak out the inputs via TTS if the action fails.
--Jason
Chad_Maggard | 2019-06-04 14:41:59 UTC | #6
Hey, Just wanted to thank you for your quick responses, really appreciated!! I have validated the inputs by having the IVR speak them.
Jason_Mathison | 2019-06-04 14:59:39 UTC | #7
Glad to (try to) help :) It is definitely up to Customer Care from here to find where things are going wrong.
--Jason
anon28066628 | 2019-06-04 15:13:22 UTC | #8
Hi Chad, something else you may do to valid inputs is write them to the conversation with the "Set Participant Data" action. It can be more precise (and less tedious :) ) than listening to TTS. The attributes appear in an array on the conversation object which you can retrieve via:
GET /api/v2/conversations/{conversationId}
The API explorer is handy for this. It's especially convenient to test your Action in Architect this way if email or SMS flows are an option, since they re-use the same conversation ID on subsequent replies after you disconnect them in your test flow.
system | 2019-07-05 15:13:25 UTC | #9
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 5262