Execution Date (or Key Pointer Column) Missing from Generated Report

What This Skill Diagnoses

Two distinct, independently occurring root causes can make a key pointer column disappear from generated reports even when the field is visible in the repository view:

1. Key pointer is_visible = False (most common for Execution Date): The "Execution Date" key pointer for the workspace has been toggled to is_visible = False via the contract metadata settings page. The backend filters key pointers by is_visible=True before including them in report columns. The UI still shows the column in the repository view and "View Columns" — this mismatch is a known UX gap.

2. Frontend columns_filter category routing bug: When "Select visible columns" is used, the frontend sends "Execution Date" in columns_filter under KEY_POINTERS with the display label "Execution Date", instead of sending it under GENERAL with the slug "execution_date". The backend only recognizes execution_date under GENERAL as the standard execution date column and ignores it when it appears under KEY_POINTERS.

Critical UX nuance (confirmed Mar 2026): For non-metadata-enabled workspaces, the Execution Date column only appears in reports when the associated key pointer is active (is_visible = True). Even when disabled, the field remains visible in the repository view and in "View Columns", creating user confusion.

Available MCP Tools for Investigation

BigQuery — Key Pointer State

⚠️ Run BQ queries one at a time — parallel execute_sql calls return 500 errors.