postExecute a decision
Runs the decision using the deployment routing configured for the selected environment. Environment configuration variables are resolved for the run. A deployment and routing must exist; sub-decisions cannot be executed directly. The call is synchronous and persists an execution. Check status even on HTTP 201: a node failure can return FAILED with result.error and a trace. Hard engine failures can instead return a non-2xx error. Successful runs normally omit trace. Send an Idempotency-Key header to retry safely: a repeated key returns the stored execution without running the decision again.
Required service-token scope: execution:write. End-user access is checked against workspace policies. Send a Bearer token and the X-Workspace-Id header.