Hi,
We're on TDI version 7387.1, using a TimeXtender REST Data Source in an Ingest instance to pull data from a paginated REST API (cursor-based pagination + a changed_after query parameter driven by a Dynamic Value SQL query).
We want to run a post-execution SQL step (updating a small watermark/control table used by the Dynamic Value query) only after the transfer task has completed successfully - not before, and not if the run fails partway through.
Our specific questions:
1. Is there a supported way to attach a pre- or post-script (Script Action) directly to a REST data source's transfer task in an Ingest instance, similar to how Script Actions work on tables in a Data Warehouse/Staging instance?
2. If this isn't natively supported on Ingest transfer tasks, what is the recommended pattern for reliably running a SQL step only after a specific ingestion task succeeds, when scheduling through Orchestration? We've seen the "dummy table with pre/post script" workaround mentioned in the community for execution packages - is that still the recommended approach for Ingest tasks specifically, or is there a cleaner option (e.g. an Orchestration-level post-step, or a condition based on the ingestion task's success status)?
3. Does Orchestration expose the success/failure status of an individual ingestion task in a way that a subsequent step could be conditioned on (so the watermark update only fires on success)?
Thanks in advance for pointing us in the right direction.
Best regards,
Bjørn A.
