Skip to main content
Sign inDownload

Run a column

Run enrichment capabilities against rows in the open table. Scope the batch from the toolbar Run menu or let auto-run fire on new and updated rows.

Toolbar Run opens a compact menu: pick scope (first 10, all unenriched or error, or force overwrite), then confirm spend when approval is required.

Manual vs auto-run

ModeBehavior
Manual-runYou choose when to run from Run or the column menu
Auto-runNew or edited rows enqueue when required inputs are present

Switch run mode from the table chrome or status bar when your workspace allows it.

Run menu scopes

Open Run in the table toolbar (Play icon, right cluster):

  1. First 10 rows — quick sample against the current view
  2. All unenriched or error — skip cells that already succeeded
  3. Force (overwrite all) — re-run every visible row; needs confirmation

The menu shows the capability name and provider logo, not a generic "enrichment column" label.

Column header Run uses the same scopes for that field only.

Preview and approval

Paid workspaces may require approval before credits spend or external egress. You see a preview of row count and cost class before execution when policy requires it.

See Approvals and Permissions.

While a job runs

  • Status chrome shows progress for the active table run.
  • Stop cancels pending queue work only.
  • Responses already returned from the provider are written and kept.
  • Shared Appenda credits exhausted mid-job stop the remainder hard.

When the job finishes, one entry appears in Version control.

Result details

Click an enrichment cell to open the result inspector: capability label, HTTP status, nested JSON (expand objects; copy per field or copy-all for the row payload). Use prev/next row chevrons to walk the column.

FAQs

Does Run use my current filter?
Yes. Row counts in the menu respect the active view filter unless you pick an explicit row range through an agent tool.
Why is a row still empty after Stop?
Stop does not roll back cells already written. It only prevents not-yet-sent rows from running.
Can I run during CSV import?
Import can opt into run-after-import. See Import for the job summary commit shape.