We use the Upload Files runtime input step to push a large binary artifact mid-pipeline to a controlled location, then pull it back later in a downstream pipeline (for example, during an image build). Today this step caps at 100MB combined per step and 50MB per individual file, with no way to request a higher limit.

We'd like a supported path to raise this limit for our account, similar to how other execution limits can already be raised on request. Our own internal policies require certain artifact types to go through a specific scanning-compliant repository rather than general-purpose object storage, so a larger size cap on this step (ideally 1GB or more) would let us move this workflow onto Harness instead of keeping it on our previous CI tool. There's a related request already tracked for expanding supported file types (including zip); this one is specifically about the size cap.