Skipped runs and restarts

A run does not load what it cannot run. When a step or a table sync is left out, DataMind records the reason instead of loading anyway. This page lists the reasons you read in run logs and node lists, and what a restart of the same run repeats.

Why a transformation run is skipped or refused

A production run executes a step only when the transformation is validated and its schedule is on. A test run must match the test that started it. When a step is left out, the run shows why:

• ETL is not validated, skipping: the transformation has not passed validation yet. Test and finalize it first, as Build, test and finalize a transformation describes.
• ETL is not on schedule, skipping: the transformation is not on its schedule. Turn the schedule on before the next run.
• Skipped Due To Previous Error: a step this one depends on failed or was skipped, so this step is skipped too. Fix the earlier step, then restart the run.
• Transformation ... not found: the transformation behind the step cannot be found. Check that it still exists before you run again.
• Wrong Job ID: a test run was started against a different job, so it is refused. Start the test again from the transformation.
• Node Already Run: the step already finished in this run. See the next section.

What Node Already Run means

Restarting a run does not begin from zero:

• A step that finished in an earlier attempt keeps its result and is not repeated; the run reports it as Node Already Run with the reason Transformation ... has already run.
• A step that never finished is attempted again, including failed and skipped steps.
• Every restart raises the run's restart count, shown on the run.

Why a table sync was skipped

A table sync that does not load shows as Skipped in the Sync Log, and its Note column gives the reason. The reasons you can read:

• Skip Reason: Synchronize Option Is Disabled: the table's Synchronize switch is off, so a scheduled run skipped the table. A sync you start by hand for a single table can still start. Switch Synchronize back on in Table > General to restore scheduled loads.
• Skip Reason: Table Is Not Deployed: the table is not deployed, so it cannot sync. Deploy it first, as Deploy a table describes.
• Skip Reason: Node Already Run: the table already finished in that run. Start a new run to sync it again.
• Skip Reason: Table Not Found In STAGING_TABLE: the run cannot find the table's load setup. Refresh the data source with Sync Schema, then sync the table again.

When several reasons apply, the Note joins them with a semicolon. See Run, stop and troubleshoot loads for the sync log and its statuses.

PII columns and test runs

When a table has columns flagged as personal data, a production run also tokenises their values after the load finishes. A test run does not tokenise: it stops after the staging copies.

Questions, answered

What does "Node Already Run" mean?

The step or table already finished in that run, so DataMind keeps its result and does not run it again. To make it run again, start a new run. Runs and their results are watched on Deploy, run, truncate and monitor tables.

Why was my run skipped with "ETL is not validated, skipping"?

A production run executes only a transformation that has passed validation. Test the transformation, finalize it, then run again, as Build, test and finalize a transformation describes.

Why was my run skipped with "ETL is not on schedule, skipping"?

The transformation is not on its schedule, so the run leaves it out. Turn the schedule on before the next run.

What happens when I restart a run?

The same run continues. Steps that finished keep their result and are not repeated, and steps that never finished run again, including failed and skipped ones. Every restart raises the run's restart count.

Why was my table sync skipped?

Its Note in the Sync Log starts with Skip Reason: and lists the cause, such as Table Is Not Deployed or Node Already Run. Follow that reason, then sync again.

Why does a sync Note list several skip reasons?

More than one cause can hold at once, and the Note joins them with a semicolon. Read the whole line, fix the causes it names, then sync again.

Can a table sync start while its Synchronize switch is off?

A scheduled run does not: it skips the table with Skip Reason: Synchronize Option Is Disabled. A sync you start by hand for a single table can still start. See Run, stop and troubleshoot loads.

Do test runs tokenise PII columns?

No. A test run stops after the staging copies, so no PII tokenisation runs. A production run tokenises flagged values after the load finishes.

Why was my step skipped after another step failed?

A step that depends on a failed or skipped step is skipped with Skipped Due To Previous Error. Fix the earlier step, then restart the run. Workflow runs report skipped nodes in their own words; see Workflows.

What does "Wrong Job ID" mean?

A test run was started against a different job, so it is refused. Start the test again from the transformation.