Skip to Content
Raydo

Troubleshoot Data Analysis workflows

Check the table contract, analysis validation and project delivery before sharing results.

The built-in analysis.workflow.run entry expects a question and a boundedTable with columns and rows. The input contract specifies up to 128 columns and 5,000 rows. The local executor needs at least one numeric column. If the run rejects its input or a chart looks sparse, inspect the table passed to the analysis step. Confirm row scope, field types, missing values and any normalization performed upstream.

Check analysisResult and validation before interpreting the chart. Verify that `analysisResult.dataset.numericColumn` matches the metric you intended to summarize. This executor picks the first column with numeric values. The built-in run handles descriptive analysis and applies checks against causal language.

For a handoff, open the report or derivative you intend to share and check the output’s delivery information and artifact ID in the run. Include the question, scope and supporting figures in the reviewed result.

On this page

Troubleshoot Data Analysis workflows