Create a Timextender SaaS package¶
A Timextender SaaS package runs an execution job in Timextender Data Integration. Where the Ingest, Prepare and Deliver types each run one stage, this type runs a job that TDI itself defines — typically several stages together.
Which of the four TDI types do I want?
Use Timextender SaaS when TDI already has an execution job that does what you want, and you only need orchestration to start it at the right moment.
Use Ingest, Prepare or Deliver when you want the stages as separate orchestration steps — so a failed ingest visibly stops the transform, and each stage can be retried on its own.
The second shape gives better logs and finer retries; the first is less to maintain when TDI already owns the sequencing.
Before you start¶
A Timextender Data Integration connection in the workspace, and an execution job defined in that instance.
Steps¶
Screenshots stop at the data provider
The images are real but end there: the execution-job list is empty for the connection available on our test environment, so the job selection and the steps after it have no screenshot yet.
1. Create the package¶
Orchestration → Packages → Create, then Timextender SaaS from the Timextender area.
2. Choose the connection¶
Select the Timextender Data Integration connection to use.
3. Choose the execution job¶
The Timextender Data Integration execution job to run.
The refresh button re-reads the list from TDI.
4. Save¶
Saves as a Draft.
Best practices¶
Keep one connection per TDI environment and pick the right one per package, rather than repointing a shared connection when promoting.
Name the package for the outcome, not for the job's internal name.
Prefer the three-stage types when you need visibility. One SaaS package that runs a multi-stage job is one line in the execution log; three packages tell you which stage failed.
Troubleshooting¶
The execution-job list is empty. The connection cannot reach TDI, its API key has been revoked, or no execution job exists in that instance. Check the data provider first, then refresh.
The job exists in TDI but is not listed. The connection points at a different TDI instance — commonly Test rather than Production.
Authentication failures after working fine. The TDI API key on the data provider has expired or been rotated. Fix it there; packages pick up the new value without editing.
Reference¶
Fields¶
| Field | Required | Notes |
|---|---|---|
| Data provider | Yes | Timextender Data Integration connection |
| Execution job | Yes | Read from TDI; has a refresh button |
Validation: Please select a Timextender Data Integration connection, Please select an execution job.
Related¶
Discussed in the community
Looking for related questions…
Didn't find your answer? Ask the community about this page — questions are answered by Timextender experts, partners and other users.