We are using a REST data source with dynamic values to fetch data for approximately 12,000 records, where each record corresponds to an individual API call.
Occasionally, we encounter issues with the API provider where some calls return a 400 error. Unfortunately, it’s unpredictable which dynamic values will cause these errors.
Currently, it appears that the TimeXtender REST data source stops processing upon encountering a 400 error, resulting in a "Completed with errors" status.
Is there a way to configure the REST data source to continue processing the remaining dynamic values, skipping over those that result in a 400 error? Ideally, it would also log the calls that failed for review.
Best regards, Pontus
Originally posted on the Timextender Community (Gainsight), 2025-01-13.
The dynamic values that causes the error seems to be correct, and I guess that there’s an issue on the providers side that causes the error. The 400 response we get has an error stacktrace in the response body.
We are reaching out to the API provider about this to hopefully fix it on their end, but functionality to let the REST connector skip (and log) errors would be useful. If that’s not available, we will try to filter suspect dynamic values in the dynamic values query.
It would be great to have functionality for handling errors. When using dynamic values some APIs will return 403 error when user doesn’t have access to the endpoint, or there is no record for that dynamic value. It can often be related to newly created entries, so not always easy to filter away manually.
Maybe a simple checkbox to be able to go to next dynamic value upon error. Or more advanced, to be able to make a list of error codes and the handling: