Skip to main content

Set pipeline memory

PUT 
/platform/pipeline/:pipelineId/memory

Update memory allocation for every job in the pipeline. This can help with OutOfMemoryError, killed containers or Java heap exhaustion. Source guidance says changes apply on the next execution; more memory does not repair invalid credentials or source schemas.

Example body: 4096 MB​

{
  "amount": 4096
}

Contract caveat​

The source documents a public API maximum of 12000 MB and a 400 error above it. The shared imported Memory.amount description instead says max 30720 and has no schema maximum. Do not treat the larger number as a verified deployed allowance; confirm with support before requesting higher allocations. Missing pipelines are documented as 404. For one job use Update job memory.

Request​

Responses​

Memory updated