The Run Log in DESelect Segment is a detailed activity log that records all segment runs—both successful and failed. It serves as a central reference point for tracking the execution of selections, making it easier for users to monitor performance, troubleshoot errors, and verify outcomes.
This also helps track the changes made to the Selection after each run. By comparing the current SQL query with the previously generated one, you can identify the modifications made in each run.
To check this, go to the overview screen and go to the Last Run column and click on the date.
What you can typically find in the Run Log?
-
Timestamp: Shows the exact date and time when the selection was executed.
- Trigger: Identifies if the Selection run is manual or scheduled.
- Source: Shows if the Selection run is a Selection or Waterfall Selection.
- Status: Shows whether the run was successful, failed, or in progress.
If you click on See Details, you can see more information such as; -
User: Displays the name or email of the user who ran the selection.
- Record Count: The number of records retrieved or inserted into the target Data Extension.
-
Error Messages: If a run fails, the Run Log will capture and display the error message for easy troubleshooting.
- SQL: Shows the generated SQL on this specific run.
Why Is the Run Log Useful?
-
Auditability: Track who ran what and when inlcuding the query changes made on the runs—a vital feature for teams working collaboratively.
-
Debugging: Identify errors and root causes quickly without needing to check complex SQL queries.
-
Data Validation: Confirm the number of records written to the Target Data Extension matches expectations.
Comments
0 comments
Please sign in to leave a comment.