Quick: require approval for a governed write
Publish a supported source-write action with an approval policy, submit a request, collect eligible approvals and inspect execution and reconciliation receipts.
This recipe uses the governed-action API or available MCP tools. It is not a per-node Studio pause recipe. The current governed-action target is a source write through the Iceberg adapter; it is not a generic approval wrapper for S3, every connector, or ontology materialization.
Prerequisites: a project, a supported transactional-table endpoint, enabled source writes, an approved policy, actor grants, and a current source snapshot.
- Create an action contract for the endpoint, with valid input/output schemas, required permissions, and an approval policy naming owner/admin roles, minimum approvals, and self-approval behavior.
- Publish the action version before submitting requests.
- Submit the source-write input and an idempotency key for this business operation. Include the expected snapshot from the immediately preceding read.
- Have eligible workspace members approve the request with a reason. Meet the configured approval count and self-approval restrictions.
- Execute the approved request and inspect its receipt.
- If the outcome is uncertain, reconcile the operation before retrying.
Approval of a write policy, a Studio asset change, and this action request are separate decisions. See Governed actions for the full contract and current backend boundary.
Quick: pipeline from Postgres to S3
Configure Postgres and S3 endpoints, review a bounded extract pipeline, save and run it, verify the output object and schedule recurring execution.
Getting help
Prepare a support report with scope, run or proposal identifiers, expected versus actual results, exact diagnostics and version information.