feat: add max_concurrent_active_run_count field to Schedule message

Google APIs · copybara-github · commit 725496d32a35 · 2026-02-06T10:59:16.000-08:00
PiperOrigin-RevId: 866530570
diff --git a/google/cloud/aiplatform/v1beta1/schedule.proto b/google/cloud/aiplatform/v1beta1/schedule.proto
@@ -1,4 +1,4 @@
-// Copyright 2025 Google LLC
+// Copyright 2026 Google LLC
 //
 // Licensed under the Apache License, Version 2.0 (the "License");
 // you may not use this file except in compliance with the License.
@@ -164,6 +164,14 @@ message Schedule {
   // execution of the operations/jobs created by the requests (if applicable).
   int64 max_concurrent_run_count = 11 [(google.api.field_behavior) = REQUIRED];
 
+  // Optional. Specifies the maximum number of active runs that can be executed
+  // concurrently for this Schedule. This limits the number of runs that can be
+  // in a non-terminal state at the same time.
+  // Currently, this field is only supported for requests of type
+  // CreatePipelineJobRequest.
+  int64 max_concurrent_active_run_count = 21
+      [(google.api.field_behavior) = OPTIONAL];
+
   // Optional. Whether new scheduled runs can be queued when max_concurrent_runs
   // limit is reached. If set to true, new runs will be queued instead of
   // skipped. Default to false.
