Problem
Downstream teams read the batch output while it's being written and get Frankenstein data: half last night's run, half tonight's, blended together with no way to tell which is which. It gets worse when a run fails halfway through; the partial output is already visible to anyone reading at that moment. Design the publish path so a consumer always sees exactly one complete run, and a failed run never corrupts or partially overwrites the last good output.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.