Jobs & Executions

Hello,TimeXtender 20.10.31.64ODX: 20.10.31We are currently running a database on hyperscale with 12vcores and premium memory optimized hardware. ODX is a data lake.We are running execution packages on 4 threads and we want to reduce our odx transfer times as that is out biggest impact right now.This is an example of a load. I am seeing long ODX transfer times for very small tables that I cant find the cause of or explain.We have alot of small tables (see example below) that is taking 1-3 minutes, while some tables doing data cleansing on 1million + rows is doing it in the same amount of time. See this small table that is 400 rows, no transformations and only 10 columns. 

Hi team, I want to create a new enviroment variable that I used to do in the old version, but with new version it changed. The idea that create a new enviroment varible, and configure on execute package, the variable check dev enviroment or prod enviroment and if it prod the execute package will run. My Version isHow can I do that?

We have recently updated a TimeXtender version from 20.1047 to 20.10.74 and was successful for Development and QA but after updating Production the SSIS Packages are not executing. Development and QA have the same version of SQL as Production. The execution of SSIS Packages is setup through External tasks. The only relevant information I have found so far regarding this issue is here (https://legacysupport.timextender.com/hc/en-us/articles/360000169786-Troubleshooting-Upgrade-Issues) but am not sure how the steps under heading ‘Cannot deploy or execute SSIS packages’ would resolve the issue. Anyone else run into this?

Hi,We are trying to access ODX execution history (backlog / queue / duration / errors) for log analytics purposes.We understand from documentation and release notes that the local ODX backlog (Backlog.sqlite) has been removed / moved in newer ODX versions, and that execution metadata is now handled differently.However, we are currently unable to locate where this information can be accessed programmatically.Additionally, in the TimeXtender Portal, we do not see the menu optionAdmin → Security / Permissions, so we are unable to: verify roles/permissions access or inspect the API for execution data Could you please help clarify: Where ODX execution history (status, start/end time, duration, errors) is stored in newer ODX versions Whethe

I am struggling with Circular References.Finished executing project 'Discovery_Hub' Execution Package 'Report Booking' Execution failed Start Time : 8/21/2025 11:52:42 AM End Time : 8/21/2025 11:52:42 AM on server: TX-SERVER-DEV -Execute Execution Package Report Booking 'Failed' 'Execute DSA DSA_F.Management Data Cleansing Rules' has a circular relation with the following steps: 'Execute DSA DSA_TX.sub_agrDIM_RentContract Data Cleansing Rules' 'Fill Aggregate Table DSA_TX.sub_agrDIM_RentContract' 'Execute DSA DSA_F.RentContract Data Cleansing Rules'The execution job Report Booking uses DSA_F.Management, but not DSA_TX.sub_agrDim_RentContracts.I have also tried excluding DSA_TX.sub_agrDim_RentContracts from the execution job, but it still fails. What i find strange is that when i run the following tables individually, i do not get any errors:DSA_F.Management  DSA_TX.sub_agrDIM_Rent

Hello,TimeXtender version 20.10I have a customer that previously had only one project (lets call it Project A). However they have now taken out certain parts of that project into new ones (Project B and Project C).Previously to be most effective we could run everything in project A in one execution package. Now with there being 3 projects in total this can’t be done (as far as I know). B + C needs to complete before project A can run. We want to run it as part of one scheduled trigger so the only way I have found to do it is as follows:Project B runs => when done triggers project C package with external step => project C package runs => when done triggers project A package with external step.Most optimally would be for B + C to run at the same time and then trigger A, but we do not want to create a complex custom solution with command prompt/powershell scripts or building logic off the repository which is the only

This is the error I am facing when executing any Prepare package (no issue with executing Ingest packages) from the Orchestration portal: ​​​​​​Error I have tried resolving the problem with troubleshooting below, but I still get the same error:  Suggested troubleshootingAny further suggestions on how to handle the issue?We run Data Integration 6935.1 and Ingest 6935.1 Thanks

When running an execution and it fails in a Tabular, isn't it possible to continue executing the other tables (which are of course not a source for the failing Tabular). Now in our process the execution stops, but the tabular is just a last  step for a few tables, not for all other tables. 

We have a table which is guarded on deployment and on execution. When we run a manual execute on this table we get the message that this table is guarded, therefore not executed. This table is in a nightly execution and we don't expect this table will be executed because of the guard on execution. But we are dumbfounded that during the nightrun it is executed (and runs in an error). What are we doing wrong?

Hello,  I’m looking for a query/view/stored procedure that can be used to query the data lineage / data flow.I would like to have the source to target mapping etc in a report/overview instead of in the GUI.So, I can easily report on the tables that are used to build the table in the next layer. Anyone an idea? Thank you,Gert    

Dear Sir,Our client upgraded TX to version 6766.1.Now their scheduled job executions stop working.They are having an issue with thier Scheduled Jobs.Running the jobs manually works fine.Please help, is there a specific Log to check in TX to understand what is causing the issue ?Does an upgrade solve this known issue ?We have released a bug fix for this in 6698.1. Please upgrade, and see the below release notes for reference:TimeXtender Desktop 6698.1Hope to hear from you.Regards,Arthur

Hi,It seems that Exmon/TX Orchestration has hung in some way.Nothing is running in the ODX  But in TX Orchestration a job is still running and block everything else in the same package. Is there a way for me to “reset” this manually or is this a support case?I have restarted the ODX service but that did noting.

How can I stop this exmon execution? Restarting or terminating the execution service did not resolve the issue.

TimeXtender Data Integration 6848.1Ingest Service 6848.1 We are experiencing issues with ingest transfer (from ingest instance to prepare instance) in our warehouse, where executions that normally take a couple of minutes get stuck on Ingest Transfer task for hours at a time. This mostly occurs when the table we execute in the prepare instance has mappings to a data source that at the same time executes in the ingest instance (even though that specific table does not execute at that time).Both the Ingest instance and the Prepare instance use SQL Server storage, hosted on the same VM as the data integration service and the ingest service. The Prepare instance uses ADO.net transfer. There are no suspended queries on the SQL Server while the execution is stuck. I’ve also checked perfmon for CPU performance: the CPU averages 80 % and the processor queue length averages 6 (ranges from 0 to 16) during executions that get stuck. Our VM has 4 vCores.

Hi support,I am experiencing some strange behaviour when the Scheduler service wants to start execution packages. The following is happening:the schedule is supposed to start at every full hour. I know that it can take up to 2 minutes for an execution to actually start. Until last monday 18:00 everything was fine. The packages started within 2 minutes and were finished within 10 minutes. After last monday 18:00, we are experiencing a delay in the start. Almost anytime the packages starts, it takes a 12 minutes delay. It also looks like the execution takes way longer than 10 minutes. However, when I look at the gantt chart, I see it still takes up to about 10 minutes to finish.

I wanted to clean the jobs in  TX Integration version 6822.1. When I deleted the last job, the folder disappeared and i am not able to add a job anymore. anyone has a solution for this issue? 

Hello, When you have multiple endpoints configured in the portal and endpoint B uses dynamic values from endpoint A, the the data on demand functionality doesn't work for tables that need endpoint B. Tables derived from A get the data on demand just fine. The exception message says: "OnDemand execution failed for data source '<datasource>' table '<table>' was not executed” I encountered this in a customer environment and then tried to replicate it locally in my sandbox setup. To my surprise, the data on demand worked in my sandbox. However, I had an older version of TX installed. I updated to the latest version on my local laptop and then encountered the exact same problem. This would suggest that it’s a bug in the new version.  My version number for TX is 6848.1. 

As of this week we encounter several errors in TimeXtender Data Integration (6766.1) and the TimeXtender Serice Configuration. When we add a execution package in deliver instances, deploy the deliver instance, and want to add this execution in the service configuration, we get this error when we try to save:We have access to this folder and can edit this file.Next error that arises is the invalid jobs in our tx data integration:Everything worked correct last several weeks, we didn't change anything. Any idea on how to solve these probles?

Hi all,We are unable to run two execution packages concurrently on the same instance. They are scheduled using Jobs. The packages have no common tables involved. We have made sure to check the other package under “Concurrent packages” under Edit Execution Package (and deploying after).Is running packages concurrently supposed to work when scheduled using Jobs?Will it be supported with Orchestration?Thanks for any input!Version: 6766.1

It seems like we have packages within a process which are stuck on “running”:Exmon DG DesktopIf I check the “Process Queue” in the webportal, like this post suggested, I can’t find anything running.Is there another way to stop these packages? Or maybe they are not running at all, the desktop application just says so.We’ve tried to restart the virtual machine where the services are running.We’re running TimeXtender Data Governance 23.3.0.40 (aka Exmon) and TimeXtender Data Integration 6814.1. 

Is it possible cancel a Job in some of these status? 

All Execution packages with a schedule do not start at the time given. It starts always seconds to minutes later than the schedule indicates. Why doesn't it start according to the schedule?It happens with almost all packages. It also varies by package. The same package can start seconds later or 2 minutes later. For example: in the screenshots you can see that the package always starts later than 05:00 as scheduled. 

Hi all,I have a customer that has to deal with an unreliable source system. During transfering specific query tables, it sometimes fails. As there is no retry option on this level, at least we can do right now is to inform the customer that things went wrong.  Unfortunately the TimeXtender API does not tell us there is anything wrong with this run. The “State” is 2, and all the child “JobExecutionLogs” child entries below the job itself all have the “Severity” value of 0. Does someone recognize this situation? Anything we can do differently to inform the customer?

Good DayIs there a way to be notified when a scheduled Execution Package does not run on the scheduled time?We had a scheduled package not able to run due to a lock on a table but were not aware as there was no error on the job since it was not able to start. Would like to be made aware of these issues instead of having to check each day to see if scheduled jobs ran.Kerry

I have a generic stored procedure that does some custom post processing based on the table that has just been reloaded (Executed).  The stored procedure takes a parameter "TableName".  I've created a Script Action that executes the stored procedure.  I need this Script Action to run as a Post Step after the last execution step is run for one of several tables.  I can create one script action per table with the tablename hardcoded, but I've got a lot of tables to work with and would really prefer do this as a parameter containing the current table name.  Is the currently executing table name available in a system parameter somewhere and/or is there a way to create one that can be referenced by a script action?