Skip to main content
To homepage To homepage
SUBMITTED

Retry Step functionality in ODX Server Transfer Task

Related products:TimeXtender Data Integration
  • July 25, 2024
  • 1 reply
  • 32 views
erik.van.mastrigt
TimeXtender Xpert
Forum|alt.badge.img+3

With Exmon it is possible to retry a Job if it (partially) fails.

 

DWH execution packages can be configured that steps will be retried a couple of times before the package fails.

Currently there is no possibility to retry streps in an ODX Transfer Task. If the Transfer Task fails (or completes with errors), the only thing you can to is configure Exmon to retry the full Transfer Task. This means that all tables in the Task will be reloaded, not only the one that failed.

If a data source has many tables, it is quite inefficient and time-consuming to re-load all tables if just one failed in the previous attempt.

Especially REST API endpoints sometimes simply throw an error. A retry after a couple of minutes makes that the load ultimately succeeds, where you don’t want to re-load all endpoints that already have been loaded.

 

I found some other questions/ideas that are highly related to this idea, but are not too explicit in what functionality is needed. Hence a new idea.

https://support.timextender.com/ideas/fail%2Dretrying%2Dexecution%2Dmessage%2D1199

 

1 reply

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+8
  • rory.smith
  • TimeXtender Xpert
  • July 26, 2024

As ODX Tasks will often contain multiple tables and the usage of on-demand may make it harder to track what tables were contained in a task, being able to retry individual steps becomes more important. With API sources it is fairly common to get some kind of a “system busy, try again later” result. If you then need to retry all calls, you are adding to the load on the source.

As making separate ODX Tasks for each table will make it impossible to load many tables at once, there is no real workaround for this at the moment.

    Terms and ConditionsAccessibility statement