transformations
Execution logs and summaries of transformation runs.
List transformation execution logs
Returns the transformation execution log entries for the given reference id within an optional time range, together with the total item count. Both bounds accept an ISO-8601 instant or a relative expression (now, now-30m, now/d), resolved at request time in the given time zone - so a stored filter of 'the last 30 minutes' stays the last 30 minutes.
Read the raw designer response of one execution
Returns the stored designer response of a single execution log record - the whole response for a failed execution, only the runtime measurement for a successful one (HET-2009). Kept out of the listing endpoints on purpose (HET-1709): the response of a failed execution can still be large, and it is displayed only when a user opens the raw JSON of one record. The reference id is required and checked against the record, so the access rights of the object the execution belongs to apply here exactly as they do for the listing.
List all transformation execution logs
Returns transformation execution log entries across all objects within an optional time range, optionally filtered by object type (workflow vs. virtual signal), together with the total item count.
Summarize transformation executions per object
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.