feat: add max_concurrent_active_run_count field to Schedule message · googleapis/googleapis@725496d

File tree

1 file changed

lines changed

  • google/cloud/aiplatform/v1beta1

1 file changed

lines changed

Original file line numberDiff line numberDiff line change

@@ -1,4 +1,4 @@

1-

// Copyright 2025 Google LLC

1+

// Copyright 2026 Google LLC

22

//

33

// Licensed under the Apache License, Version 2.0 (the "License");

44

// you may not use this file except in compliance with the License.

@@ -164,6 +164,14 @@ message Schedule {

164164

// execution of the operations/jobs created by the requests (if applicable).

165165

int64 max_concurrent_run_count = 11 [(google.api.field_behavior) = REQUIRED];

166166
167+

// Optional. Specifies the maximum number of active runs that can be executed

168+

// concurrently for this Schedule. This limits the number of runs that can be

169+

// in a non-terminal state at the same time.

170+

// Currently, this field is only supported for requests of type

171+

// CreatePipelineJobRequest.

172+

int64 max_concurrent_active_run_count = 21

173+

[(google.api.field_behavior) = OPTIONAL];

174+
167175

// Optional. Whether new scheduled runs can be queued when max_concurrent_runs

168176

// limit is reached. If set to true, new runs will be queued instead of

169177

// skipped. Default to false.