Create a new Executions instance.
Function for making API requests
Count the scenarios and executions across an organization whose module input/output data matches a query.
The organization ID to search in
Search expression and optional filters (team, time window, scenarios, status)
Promise with the total and per-scenario counts
Get details of a specific execution.
The scenario ID the execution belongs to
The unique ID of the execution to retrieve
Promise with the execution details
Get detailed result of a specific execution.
The scenario ID the execution belongs to
The unique ID of the execution to retrieve
Optionaloptions: GetExecutionDetailOptionsOptional parameters, e.g. a byte budget for the returned outputs
Promise with the detailed execution result
Get details of a specific execution for an incomplete execution.
The incomplete execution ID
The unique ID of the execution to retrieve
Promise with the execution details
List executions for a scenario.
The scenario ID to list executions for
Optionaloptions: ListExecutionsOptionsOptional parameters for pagination and filtering by status or time range
Promise with the list of scenario executions
List executions for an incomplete execution.
The incomplete execution ID to list executions for
Optionaloptions: ListExecutionsOptionsOptional parameters for pagination and filtering by status or time range
Promise with the list of executions related to the incomplete execution
Search executions across an organization by time window, status, scenario, or error message.
The organization ID to search in
Optionaloptions: SearchExecutionsOptionsOptional filters (team, time window, error message, scenarios, status) and paging
Promise with the matching executions, newest first
Full-text search the module input/output data of executions across an organization. Available on the Pro plan and above.
The organization ID to search in
Search expression and optional filters (team, time window, scenarios, apps, modules, status) and paging
Promise with the matching executions and their matching IO-data records
Full-text search the module input/output data of a single execution. Available on the Pro plan and above.
The organization ID the scenario belongs to
The scenario ID the execution belongs to
The execution ID to search in
Search expression and optional filters (time window, apps, modules, status)
Promise with every matching IO-data record and the execution's metadata
Class providing methods for working with Make executions. Executions represent the running instances of scenarios and provide information about each time a scenario was executed.