Skip to main content
To homepage To homepage
Solved

How to Handle 400 Errors in TimeXtender REST Data Source with Dynamic Values?

  • January 13, 2025
  • 5 replies
  • 67 views
Pontus Olausson
Contributor
Forum|alt.badge.img

Hi,

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

Best answer by Pontus Olausson

Hi ​@Thomas Lind 

We use dynamic values from query.

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.

 

 

View original
Did this topic help you find an answer to your question?

5 replies

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Thomas Lind
  • Community Manager
  • 1031 replies
  • January 13, 2025

Hi ​@Pontus Olausson 

Is the setup you use a query or the dynamic value from endpoint option?

If it is from an endpoint, will the incorrect characters be empty, or just an result that contains no data?

And I am not aware of any current options to ignore an error and continue with the next.

 

Pontus Olausson
Contributor
Forum|alt.badge.img
  • Pontus Olausson
  • Author
  • Contributor
  • 17 replies
  • Answer
  • January 13, 2025

Hi ​@Thomas Lind 

We use dynamic values from query.

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.

 

 

Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi ​@Pontus Olausson were you able to resolve this with the API provider or by filtering suspect dynamic values in the query?

J
Contributor
Forum|alt.badge.img
  • jarle
  • Contributor
  • 19 replies
  • March 24, 2025

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:

Error code Handling Wait
403 Continue with next record 10 sec
429 Retry 60 sec
401 Stop  

 

Thomas Lind
1 person likes this
  • Thomas Lind
    Thomas Lind
Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Thomas Lind
  • Community Manager
  • 1031 replies
  • March 25, 2025

Hi ​@jarle 

Since that isn’t exactly the original question, you could make an idea out of this. We have had behaviors similarly to this before on data sources.

Reply


Most helpful members this week

Terms and ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings