When using SDK adapters, I find that API-level errors don't surface in job reports.
Is there some way to do that?
For example, here's an error I get from the eBay API, using the SDK console:
{"errors":[{"errorId":25709,"domain":"API_INVENTORY","subdomain":"Selling","category":"REQUEST","message":"Invalid value for pricingSummary.price.value.","parameters":[{"name":"text1","value":"pricingSummary.price.value"}]}]}
But this is the corresponding error in a job report:
Kyle Tan
SDK: Error Handling
When using SDK adapters, I find that API-level errors don't surface in job reports.
Is there some way to do that?
For example, here's an error I get from the eBay API, using the SDK console:
But this is the corresponding error in a job report:
Is there a better way to build the SDK adapter to surface these issues? Any use-able workaround ideas would also be appreciated :)
Kyle,
http://docs.workato.com/developing-connectors/sdk/authentication/custom-authentication.html#detecton
The above link might interest you.
Sharat Hegde
Kyle,
http://docs.workato.com/developing-connectors/sdk/authentication/custom-authentication.html#detecton
The above link might interest you.
Kyle Tan
`.detect_on` does seem useful to catch errors that show up under status code `200`.
But how does that surface the API-level errors so that we can see the granular details in the job reports?