Interactive And File Lanes Share The Batch Runner

Context

The same domain changes range from small selections to very large files.

Decision and Origin

Interactive requests carry at most 500 items; file jobs use durable orchestration and chunked input, with both lanes executing through the common batch runner. The origin recorded above supplies the authority for this choice; implementation evidence supplies the limits described here.

Alternative Comparison

Use durable orchestration for every small request: Small changes would incur orchestration work even when their input fits the interactive lane.

Send large inputs in API request bodies: Request and function resource limits constrain large payloads.

Consequences

The submission body selects the lane at the same operation route.

Bulk input lives in chunk files rather than per-item database rows.

File jobs lack an interactive preview, and large console selections are converted into files.