Sync Log tables

The run logs across DataMind share one table: it lists a table's or transformation's runs, and each run's status, duration, rows and errors. Use this page as the shared reference wherever you meet it; each area's own page covers its full flow.

Where you meet this table

• The Sync Log on the Settings tab of a Lake table's popup. See Run, stop and troubleshoot loads.
• The Sync Log on a Writeback table's Settings tab. See Synchronize a table and read the Sync Log; for whole workflows, see Run, schedule and monitor Writeback.
• The Test Log in a transformation's Validation step and the Run Log on its Execution tab. See Build, test and finalize a transformation.
• The Transformation Runs list in a Dimension or Fact table's popup. See Deploy, run, truncate and monitor tables.
• Whole-workflow runs, job by job, on Job runs.

Read a run's row

Each row is one run. The columns differ a little between areas; the cells behave the same way.

• Identifier and note cells copy on click: a check confirms the copy, then fades after two seconds.
• Dates read dd/MM/yy · HH:mm:ss.
• Rows shows the processed count with thousands separators.
• Note carries extra detail, such as why a run was skipped, and shows its whole text on hover.
• The error cell previews the first line of a failure, or an amber warnings badge on a finished Connect Any API load. Open it for the full text, as Error stacks and runner diagnostics describes.
• User shows the creator's email address, falling back to their login name when the email is missing.

What a run's status tells you

The Status cell colours each state, so the table reads at a glance.

Follow a run's duration

• A run that has not finished counts up live: its Duration ticks every second from the run's start, because the recorded length arrives only when the run ends.
• Pending runs do not tick; they are queued, not running.
• When a run ends, the cell shows the length it recorded, or its end minus its start.
• Lengths read in hours, minutes and seconds, like 1h 2m 3s; a length of zero shows 0s, and a length the platform cannot compute shows -.

Sort and filter the log

• Every data column is sortable and filterable; each column's filter control sits in its header.
• A filter menu keeps the values you tick pinned to the top of the list.
• Reset clears a filter, and an empty value shows as (Empty).
• The Duration column's filter is a range slider whose handles read as durations.

Stop or delete a run

The row actions sit in the last column.

• A run that has not finished offers the stop control. Screen readers name it Abort run; some areas name it for their runs, such as Abort test run and Abort transformation run in Warehouse, and Abort synchronization in the Lake. While the request is in flight the control turns into a spinner and cannot be clicked again, and some areas ask you to confirm before the run stops.
• A finished run offers Delete log entry, which removes its row from the log. It is disabled while the delete is in flight, and a row the area cannot delete shows no control at all.
• If a request fails, the message carries the server's reason for the failure.

Work through a failed load

1. Filter the Status column to the failed states, such as Error, or sort the table to find the run you are after.
2. Read the run's Status and Note cells, then open its error cell for the full message.
3. If the run is stuck and still going, stop it from its row.
4. Delete the finished rows you no longer need.

Questions, answered

Why does a running row's Duration keep counting up?

The run has not finished, so the platform has not recorded its length yet. The cell counts from the run's start and ticks every second until the run ends; then it shows the recorded length.

Why is there no delete control on a running row?

A row that has not finished offers its stop control instead. Once the run is no longer running, the delete control appears, where the area offers it.

What does the dash in the Duration column mean?

The platform could not compute a length for that run, so it shows - rather than a number that would be wrong. A run that took no measurable time shows 0s instead.

How do I copy a value from a row?

Click the value; a check confirms the copy, then fades after two seconds. Cells that hold identifiers or notes copy this way.

Why does the User column show an email address?

The column labels the run with the account that started it: the creator's email address, or their login name when the email is missing.

Where do I see why a run failed?

Its Status turns red, its Note cell carries extra detail, and its error cell previews the message; open the cell to read the whole text, described on Error stacks and runner diagnostics.

How do I narrow the table to just the failed runs?

Open the filter in the Status column header and tick the states you want, such as Error; tick several values to widen the filter, and click Reset inside the menu to clear it.