[harini-venkataraman]

What

• Pass extraction_priority from exported agentic table settings through to the executor in workflow runs

Why

• The agentic_params dict built in structure_tool_task.py omitted extraction_priority, so the agentic table executor always received None and fell back to text-only mode — even when the exported Prompt Studio project was configured for image mode. This means the cell value verifier (Agent 3.6) and image-mode prompts were silently skipped in workflow execution.

How

• Added "extraction_priority": at_settings.get("extraction_priority") to the agentic_params dict at line 545 in structure_tool_task.py

Can this PR break any existing features? If yes, please list possible items. If no, please explain why.

• No. When extraction_priority is not present in the exported settings, .get() returns None, which is the existing default behavior. Only projects explicitly configured for image mode will see a change (they'll now correctly use image mode in workflow runs).

Related Issues or PRs

• Cloud PR UN-3403 [FEAT] Agentic table extractor plugin with multi-agent LLM-powered table extraction #1914 (UN-4069) — adds the extraction_priority field to the export/clone paths

Notes on Testing

• Deploy with the companion cloud PR and run a workflow with an image-mode agentic table project to verify image-mode prompts and the cell value verifier are invoked.

🤖 Generated with Claude Code

[greptile-apps]

via Greptile

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; no new actionable issue was found.

Summary

Passes exported agentic table settings to workflow execution and keeps returned raw data.

• Workflow table runs use their exported extraction settings.
• Agentic table raw data is included in workflow results.

harini-venkataraman accepted the possible _raw_data prompt-name collision because underscore-prefixed keys are reserved by convention. Greptile withdrew that finding.

_{Reviews (5) · Last reviewed commit: "Merge branch 'main' into UN-4069-extract..." · Reviewed by Greptile}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Unstract test results

Per-group results

Status	Group	Tier	Passed	Failed	Errors	Skipped	Duration (s)
⚪	e2e-agent-kv	e2e	0	0	0	1	0.1
✅	e2e-api-deployment	e2e	3	0	0	0	14.4
✅	e2e-coowners	e2e	1	0	0	0	1.7
✅	e2e-etl	e2e	1	0	0	0	8.3
✅	e2e-login	e2e	2	0	0	0	1.2
✅	e2e-prompt-studio	e2e	1	0	0	0	11.6
✅	e2e-smoke	e2e	2	0	0	0	1.1
✅	e2e-workflow	e2e	1	0	0	0	20.3
✅	frontend	unit	654	0	0	0	22.0
✅	integration-backend	integration	1459	0	0	26	83.7
✅	integration-connectors	integration	1	0	0	7	9.3
✅	integration-workers	integration	181	0	0	1	55.8
❌	ui	e2e	0	1	0	0	0.0
✅	unit-agent-kv-schema	unit	143	0	0	0	1.8
✅	unit-backend	unit	2137	0	0	1	61.9
✅	unit-connectors	unit	82	0	0	0	11.5
✅	unit-core	unit	281	0	0	0	3.2
✅	unit-filesystem	unit	1	0	0	0	4.4
✅	unit-platform-service	unit	18	0	0	0	2.7
✅	unit-rig	unit	120	0	0	0	4.6
✅	unit-runner	unit	12	0	0	0	3.0
✅	unit-sdk1	unit	1197	0	0	0	47.3
✅	unit-tool-sidecar	unit	8	0	0	0	1.8
✅	unit-workers	unit	1647	0	0	2	134.3
	TOTAL		7952	1	0	38	506.3

Critical paths

⚠️ Critical paths not yet covered

• workflow-execution-fan-out — Multi-file workflow execution fans out to file-processing workers and rejoins. (declared coverage: no groups declared)

✅ Covered critical paths

• auth-login — covered by e2e-login
• adapter-register-llm — covered by integration-backend
• workflow-author — covered by integration-backend
• co-owner-manage — covered by integration-backend, e2e-coowners
• workflow-create-execute — covered by e2e-workflow
• api-deployment-provision — covered by integration-backend
• api-deployment-auth — covered by integration-backend
• api-deployment-run — covered by e2e-api-deployment
• mcp-server-auth — covered by integration-backend
• mcp-platform-auth — covered by integration-backend
• platform-key-whoami — covered by integration-backend
• prompt-studio-author — covered by integration-backend
• prompt-studio-fetch-response — covered by e2e-prompt-studio
• connector-register-test — covered by integration-backend
• pipeline-etl-execute — covered by e2e-etl
• usage-aggregate-read — covered by integration-backend
• usage-token-tracking — covered by e2e-api-deployment
• callback-result-delivery — covered by e2e-api-deployment