ebonding Integration - why script didn't run(inbound and outbound) for some incidents intermittently

[Priya Bonam]

inbound and outbound script didnt run seems then not updated at both ends as per ebonding integration works.

In logs i cloud see only "empty" script error as shown in log screenshot and no other error observed.

Please suggest why it meant for and why the issue?

[Arun_S1]

@Priya Bonam If you think the script is working intermittently.

1. it could be a data issue,  a field that is referenced in the script is empty or not containing the expected value.

2. Otherwise it could be possible that the REST call is made but the target instance did not receive.

3. It could be possible the data is sent to the target but that was not processed due to incorrect or missing mandatory data.

4. Could be the data is sent to target system and processed by the target system but the response was delayed and timed out and hence the response is not captured. 

My recommendation is if you know the payload that will be triggered by the script and the end points and credentials to the target system non-prod environment, try triggering the data push from a 3rd party tool like post man and see the response.

Also help me understand on the error handling mechanisms written on the script, that can help you to isolate the problem.

Please mark the appropriate response as correct answer and helpful

Thanks