Summarize transformation executions per object
GET/transformations/execution-summaries
Returns one aggregated row per workflow, virtual signal and dynamic workflow for the given time range - of those the caller may read (a dynamic workflow: every node it names); an admin also gets the rows of objects deleted since. Each row carries the last execution with its status, the execution counts broken down by status, and the mean and 95th-percentile duration. Virtual signals that carry an active scheduler job but have not executed at all in the range are included with a total of zero, because "was scheduled and never ran" is not visible in the execution log itself. A virtual signal on an active schedule counts its scheduled runs only - the runs its plot triggers are left out, as they are for the execution alarms (HET-1710); a workflow, and a signal whose schedule is paused, count all of their runs. Aggregated in the database, so the response grows with the number of objects rather than the number of executions.
Request
Responses
- 200
- 400
- 401
- 403
- default
One page of the summary rows - one row per object with executions in the time range. Aggregated, filtered by the caller's rights and sorted over all objects, then cut to the page.
An invalid filter or range, or a sort field other than objectName, lastExecutionDate, totalExecutions, failedExecutions, meanDurationSeconds or p95DurationSeconds. Without a sort field the rows come with the most failures first.
Unauthorized — the bearer token is missing, expired or invalid, or carries no role. Errors raised by the security aspects contain an ErrorDto body; requests rejected by the security filter chain may have an empty body.
Forbidden — the authenticated user lacks the required role or access rights.
the default error response