post-scenario-run

POST 
/v1/projects/:projectId/scenarios/:scenarioId/run

Starts an asynchronous economics run for the specified scenario. Always returns 202 Accepted immediately with a jobId that can be polled via GET .../run/{jobId}. Mode A (defaults): Send an empty body {} or { "wellIds": [...] }. The server uses the same UI dialog defaults for columns, report settings, and combos when the corresponding setting ids are omitted. Mode B (saved settings): Supply any subset of econSettingId, econReportSettingId, and comboSettingId. Omitted ids fall back to UI defaults for that slice. Selection: provide wellIds, or omit it to run every well in the scenario. Either way each well resolves to its base scenario-well-assignment; incrementals are not included.

Request

Responses

202

Accepted. The economics run has been queued. Poll GET .../run/{jobId} for status.

400

Bad Request. Schema validation failed, group economics was detected, General Options are missing, or no combos are selected.

404

Not Found. The project, scenario, well assignment, or referenced setting id was not found.

409

Conflict. The scenario already has an economics run in progress.

429

Too Many Requests. The tenant has too many economics runs in progress via the external API.