Run a transformation and read the Run Log

The Execution tab of a transformation runs it by hand and follows what each production run did. Open it after the transformation is finalized to start a run, watch it in the Run Log, and stop one that is still going. The whole build, test and finalize flow is on Build, test and finalize a transformation; the day-to-day actions across tables are on Deploy, run, truncate and monitor tables.

Run a transformation now

1. Open the transformation and switch to Execution, the tab next to Transformation.
2. Click Execute Now at the top of the tab. It appears once the transformation is finalized; if it is missing, finish the finalize step first.
3. In Execute Transformation, check the day on Select Date and the time on Select Time. The date starts on yesterday.
4. Check the right side under Transformation Info: the Name, the Status (Ready or Not Ready) and the Schedule (Active or Inactive).
5. Set any values under Run Parameters when the pattern is periodic. The values apply to this run only; Transformation patterns and load settings describes them.
6. Click Execute. While the request is going out, the button reads Running... and both Cancel and Execute are disabled.
7. Read the result. On success, Transformation run started successfully appears, the dialog closes and the log reloads. If the run cannot start, the dialog shows the reason above the buttons and a toast reads the reason; with no reason from the server, they fall back to Failed to execute transformation and Failed to run transformation.

Follow the Run Log

The Run Log lists the transformation's production runs.

• Only production runs appear. A test run you started while validating the transformation stays on the Validation step; see Run and monitor transformation tests.
• Each row shows the run's Log ID, Status, Rows, Error, User, Start, Finish, Duration and Snap Date. The toolbar search and the column filters narrow the list, and every column sorts.
• While a run is in progress, a Running badge appears next to the Run Log title, and the list refreshes itself about once a second until the run settles.
• Refresh data on the toolbar reloads the list by hand. If the reload fails, you see Failed to refresh transformation runs.
• The export downloads every run that matches the current filters, not only the page on screen.
• The log shows 50 rows per page; the page size can be set to 20, 50, 100 or 500.
• Your column layout (order, width and visibility) carries over between transformations; filters, sorting and the page you were on do not.
• A transformation with no production runs yet reads No transformation runs found.

To understand what a run writes into the table, see How Dimension and Fact runs write data.

Stop a running run

1. In the Run Log, click the stop button at the end of the row whose run is still going. The button appears only while a run is running.
2. In Abort Transformation Run, read: "Are you sure you want to abort this transformation run? This action cannot be undone." Confirm to stop the run.
3. Read the result: Transformation run aborted successfully, or Failed to abort transformation run with the reason when the stop fails.

From the table side, runs can also be stopped on the table's Settings tab; Deploy, run, truncate and monitor tables covers both routes.

Questions, answered

Which runs does the Run Log show?

Production runs only. A test run you start while validating the transformation stays on the Validation step; see Run and monitor transformation tests.

What does the Running badge mean?

At least one run in the log is still going. It shows while a run is Running or Pending, and the list refreshes itself about once a second until the run finishes.

The export has more rows than the page shows. Why?

The export downloads every run that matches the current filters and search, not only the page on screen.

Why can't I stop a run that already finished?

The stop button appears only while a run is running. A run that has already finished cannot be aborted; DataMind refuses the request.

Where do I read why a run failed?

Click the run's error text in the log: a failed run's Error cell opens its full stack, ready to read. To read a test run's stack and details, see Run and monitor transformation tests.

Why do the column widths carry over to another transformation?

The Run Log keeps one column layout across all transformations, so a width, order or hidden column you set once stays. Filters, sorting and the page you were on are not carried over.