Support for started_at webhook event types as they happen, not after completion
N
Nick Oakes
The workflow-completed and job-completed webhook event types only report information following a terminal state. Users wanting to track duration live (sub-entities like started_at, created_at and triggered_at) are unable to do so, and must wait until their workflow or job finishes. Would it be possible to allow limited sub-entities (listed above) for a new workflow-triggered event type?