Skip to main content
To homepage To homepage
SUBMITTED

Error handling timeXtender Rest Dynamic values

Related products:Data source providers
  • April 3, 2025
  • 2 replies
  • 68 views
J
Contributor
Forum|alt.badge.img

Also mentioned in this Q&A

It would be great to have functionality for handling errors in the timeXtender REST connector (and maybe other connectors as well). 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 0 sec
429 Retry 60 sec
401 Stop  
404 Continue with next record 0 sec

2 replies

L
Participant
Forum|alt.badge.img
  • luuk.bouman
  • Participant
  • February 19, 2026

We've encountered the same issue while connecting with two different APIs the past month. In the first instance we we're able to negotiate the response with the API developer. In the second case the developers on the other side didn't have this flexibility.

Seems valid to add a form of error handling for REST connections in the TimeXtender REST provider. Lots of APIs give error responses with dynamic values, but this doesn't necessarily have to mean that the execution in TX should break.

Would be nice to be able to add exceptions for certain error codes. E.g. set up that if the error code 400 is raised handle this by continuing with the next dynamic value, for all other errors use the default handling.

 

Vilsen,

Luuk

    E
    Starter
    Forum|alt.badge.img
    • EmilGilljam
    • Starter
    • February 25, 2026

    Would really need somthing like this.

    We get data from several api:s where small user errors in the source system could end in 500 erros when we try to get the data. 

    So a function to skip and continue with next dynamic value record would be great.

      Terms and ConditionsAccessibility statement