--- title: "ListWorkflowExecutions" method: POST path: "/gitpod.v1.WorkflowService/ListWorkflowExecutions" tags: ["gitpod.v1.WorkflowService"] --- # ListWorkflowExecutions `POST /gitpod.v1.WorkflowService/ListWorkflowExecutions` Lists workflow executions with optional filtering. Use this method to: - Monitor workflow execution history - Track execution status - Debug workflow issues ### Examples - List executions for workflow: Shows all executions for a specific workflow. ```yaml filter: workflowIds: ["b0e12f6c-4c67-429d-a4a6-d9838b5da047"] pagination: pageSize: 20 ``` ## Query parameters - `pageSize` integer - `token` string ## Request body - GitpodV1ListWorkflowExecutionsRequest — ListWorkflowExecutionsRequest lists workflow executions with optional filtering. - `filter` GitpodV1ListWorkflowExecutionsRequestFilter - `hasFailedActions` boolean, nullable - `search` string — search performs case-insensitive search across workflow execution ID and trigger type - `statusPhases` GitpodV1WorkflowExecutionPhase[] - `workflowExecutionIds` string[] - `workflowIds` string[] - `pagination` GitpodV1PaginationRequest - `pageSize` integer — Page size is the maximum number of results to retrieve per page. Defaults to 25. Maximum 100. - `token` string — Token for the next set of results that was returned as next_token of a PaginationResponse - `sort` GitpodV1Sort - `field` string — Field name to sort by, in camelCase. - `order` 'SORT_ORDER_UNSPECIFIED' | 'SORT_ORDER_ASC' | 'SORT_ORDER_DESC' ## Response `200` Success - GitpodV1ListWorkflowExecutionsResponse - `pagination` GitpodV1PaginationResponse - `nextToken` string — Token passed for retrieving the next set of results. Empty if there are no more results - `workflowExecutions` GitpodV1WorkflowExecution[] - `id` string, uuid - `metadata` GitpodV1WorkflowExecutionMetadata — WorkflowExecutionMetadata contains workflow execution metadata. - `creator` GitpodV1Subject - `id` string, uuid — id is the UUID of the subject - `principal` 'PRINCIPAL_UNSPECIFIED' | 'PRINCIPAL_ACCOUNT' | 'PRINCIPAL_USER' | 'PRINCIPAL_RUNNER' | 'PRINCIPAL_ENVIRONMENT' | 'PRINCIPAL_SERVICE_ACCOUNT' | 'PRINCIPAL_RUNNER_MANAGER' - `executor` GitpodV1Subject - `id` string, uuid — id is the UUID of the subject - `principal` 'PRINCIPAL_UNSPECIFIED' | 'PRINCIPAL_ACCOUNT' | 'PRINCIPAL_USER' | 'PRINCIPAL_RUNNER' | 'PRINCIPAL_ENVIRONMENT' | 'PRINCIPAL_SERVICE_ACCOUNT' | 'PRINCIPAL_RUNNER_MANAGER' - `finishedAt` string, date-time — A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one. All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a [24-hour linear smear](https://developers.google.com/time/smear). The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) date strings. # Examples Example 1: Compute Timestamp from POSIX `time()`. Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0); Example 2: Compute Timestamp from POSIX `gettimeofday()`. struct timeval tv; gettimeofday(&tv, NULL); Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000); Example 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime()`. FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime; // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100)); Example 4: Compute Timestamp from Java `System.currentTimeMillis()`. long millis = System.currentTimeMillis(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build(); Example 5: Compute Timestamp from Java `Instant.now()`. Instant now = Instant.now(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(now.getEpochSecond()) .setNanos(now.getNano()).build(); Example 6: Compute Timestamp from current time in Python. timestamp = Timestamp() timestamp.GetCurrentTime() # JSON Mapping In JSON format, the Timestamp type is encoded as a string in the [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset). For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017. In JavaScript, one can convert a Date object to this format using the standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString) method. In Python, a standard `datetime.datetime` object can be converted to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime) with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use the Joda Time's [`ISODateTimeFormat.dateTime()`]( http://joda-time.sourceforge.net/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime() ) to obtain a formatter capable of generating timestamps in this format. - `startedAt` string, date-time — A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one. All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a [24-hour linear smear](https://developers.google.com/time/smear). The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) date strings. # Examples Example 1: Compute Timestamp from POSIX `time()`. Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0); Example 2: Compute Timestamp from POSIX `gettimeofday()`. struct timeval tv; gettimeofday(&tv, NULL); Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000); Example 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime()`. FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime; // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100)); Example 4: Compute Timestamp from Java `System.currentTimeMillis()`. long millis = System.currentTimeMillis(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build(); Example 5: Compute Timestamp from Java `Instant.now()`. Instant now = Instant.now(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(now.getEpochSecond()) .setNanos(now.getNano()).build(); Example 6: Compute Timestamp from current time in Python. timestamp = Timestamp() timestamp.GetCurrentTime() # JSON Mapping In JSON format, the Timestamp type is encoded as a string in the [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset). For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017. In JavaScript, one can convert a Date object to this format using the standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString) method. In Python, a standard `datetime.datetime` object can be converted to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime) with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use the Joda Time's [`ISODateTimeFormat.dateTime()`]( http://joda-time.sourceforge.net/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime() ) to obtain a formatter capable of generating timestamps in this format. - `workflowId` string, uuid - `spec` GitpodV1WorkflowExecutionSpec — unresolved $ref - `status` GitpodV1WorkflowExecutionStatus — WorkflowExecutionStatus contains the current status of a workflow execution. - `agents` GitpodV1WorkflowExecutionStatusAgent[] — Effective agent configurations observed across this execution's actions. Populated only for callers allowed to administer the workflow. - `agentId` string, uuid - `codexSettings` GitpodV1CodexSettings — CodexSettings contains settings consumed only by the Codex app agent. - `model` 'CODEX_OPEN_AI_MODEL_UNSPECIFIED' | 'CODEX_OPEN_AI_MODEL_GPT_5_5' | 'CODEX_OPEN_AI_MODEL_GPT_5_4' | 'CODEX_OPEN_AI_MODEL_GPT_5_4_MINI' | 'CODEX_OPEN_AI_MODEL_GPT_5_3_CODEX' | 'CODEX_OPEN_AI_MODEL_GPT_5_3_CODEX_SPARK' | 'CODEX_OPEN_AI_MODEL_GPT_5_2' | 'CODEX_OPEN_AI_MODEL_GPT_5_6_SOL' | 'CODEX_OPEN_AI_MODEL_GPT_5_6_TERRA' | 'CODEX_OPEN_AI_MODEL_GPT_5_6_LUNA' — CodexOpenAIModel is the static allowlist of concrete OpenAI models that the Codex app runtime can select through Ona's Codex picker. - `reasoningEffort` 'CODEX_REASONING_EFFORT_UNSPECIFIED' | 'CODEX_REASONING_EFFORT_LOW' | 'CODEX_REASONING_EFFORT_MEDIUM' | 'CODEX_REASONING_EFFORT_HIGH' | 'CODEX_REASONING_EFFORT_EXTRA_HIGH' — CodexReasoningEffort is the static allowlist of reasoning efforts supported by the Codex app runtime. - `serviceTier` 'CODEX_SERVICE_TIER_UNSPECIFIED' | 'CODEX_SERVICE_TIER_FAST' — CodexServiceTier is the static allowlist of service tiers supported by the Codex app runtime. - `aiUsage` GitpodV1WorkflowExecutionAIUsage — WorkflowExecutionAIUsage contains the intelligence usage attributed to a workflow execution. - `intelligenceUsageCalculatedAt` string, date-time — A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one. All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a [24-hour linear smear](https://developers.google.com/time/smear). The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) date strings. # Examples Example 1: Compute Timestamp from POSIX `time()`. Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0); Example 2: Compute Timestamp from POSIX `gettimeofday()`. struct timeval tv; gettimeofday(&tv, NULL); Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000); Example 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime()`. FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime; // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100)); Example 4: Compute Timestamp from Java `System.currentTimeMillis()`. long millis = System.currentTimeMillis(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build(); Example 5: Compute Timestamp from Java `Instant.now()`. Instant now = Instant.now(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(now.getEpochSecond()) .setNanos(now.getNano()).build(); Example 6: Compute Timestamp from current time in Python. timestamp = Timestamp() timestamp.GetCurrentTime() # JSON Mapping In JSON format, the Timestamp type is encoded as a string in the [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset). For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017. In JavaScript, one can convert a Date object to this format using the standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString) method. In Python, a standard `datetime.datetime` object can be converted to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime) with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use the Joda Time's [`ISODateTimeFormat.dateTime()`]( http://joda-time.sourceforge.net/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime() ) to obtain a formatter capable of generating timestamps in this format. - `intelligenceUsageTotal` GitpodV1EnterpriseAIUsage - `costMicrounits` string - `credits` number, double - `currency` 'BILLING_CURRENCY_UNSPECIFIED' | 'BILLING_CURRENCY_USD' | 'BILLING_CURRENCY_EUR' | 'BILLING_CURRENCY_GBP' - `tokens` GitpodV1EnterpriseAITokenUsage - `cacheTokens` string - `inputTokens` string - `outputTokens` string - `totalTokens` string - `doneActionCount` integer - `failedActionCount` integer - `failureMessage` string — FailureMessage summarises why the workflow execution failed to operate. If this is non-empty the workflow execution has failed to operate and will likely transition to a stopped state. Deprecated: Use failures instead for structured error information. - `failures` GitpodV1WorkflowError[] — Structured failures that caused the workflow execution to fail. Provides detailed error codes, messages, and retry information. - `code` 'WORKFLOW_ERROR_CODE_UNSPECIFIED' | 'WORKFLOW_ERROR_CODE_ENVIRONMENT_ERROR' | 'WORKFLOW_ERROR_CODE_AGENT_ERROR' — WorkflowErrorCode defines error codes specific to workflows. These codes help distinguish retriable vs non-retriable errors and provide actionable information to both the reconciler and the frontend. Error code ranges: - 0: Unspecified - 1-999: Reserved for future use - 1000-1999: Environment-related errors - 2000-2999: Agent-related errors - 3000-3999: Resource-related errors - `message` string — Human-readable error message. - `meta` object — Additional metadata about the error. Common keys include: - environment_id: ID of the environment - task_id: ID of the task - service_id: ID of the service - workflow_id: ID of the workflow - workflow_execution_id: ID of the workflow execution - `reason` string — Reason explaining why the error occurred. Examples: "not_found", "stopped", "deleted", "creation_failed", "start_failed" - `retry` GitpodV1WorkflowErrorRetry — Retry configuration for the error. - `retriable` boolean — Whether the error is retriable. - `retryAfter` string, regex — A Duration represents a signed, fixed-length span of time represented as a count of seconds and fractions of seconds at nanosecond resolution. It is independent of any calendar and concepts like "day" or "month". It is related to Timestamp in that the difference between two Timestamp values is a Duration and it can be added or subtracted from a Timestamp. Range is approximately +-10,000 years. # Examples Example 1: Compute Duration from two Timestamps in pseudo code. Timestamp start = ...; Timestamp end = ...; Duration duration = ...; duration.seconds = end.seconds - start.seconds; duration.nanos = end.nanos - start.nanos; if (duration.seconds < 0 && duration.nanos > 0) { duration.seconds += 1; duration.nanos -= 1000000000; } else if (duration.seconds > 0 && duration.nanos < 0) { duration.seconds -= 1; duration.nanos += 1000000000; } Example 2: Compute Timestamp from Timestamp + Duration in pseudo code. Timestamp start = ...; Duration duration = ...; Timestamp end = ...; end.seconds = start.seconds + duration.seconds; end.nanos = start.nanos + duration.nanos; if (end.nanos < 0) { end.seconds -= 1; end.nanos += 1000000000; } else if (end.nanos >= 1000000000) { end.seconds += 1; end.nanos -= 1000000000; } Example 3: Compute Duration from datetime.timedelta in Python. td = datetime.timedelta(days=3, minutes=10) duration = Duration() duration.FromTimedelta(td) # JSON Mapping In JSON format, the Duration type is encoded as a string rather than an object, where the string ends in the suffix "s" (indicating seconds) and is preceded by the number of seconds, with nanoseconds expressed as fractional seconds. For example, 3 seconds with 0 nanoseconds should be encoded in JSON format as "3s", while 3 seconds and 1 nanosecond should be expressed in JSON format as "3.000000001s", and 3 seconds and 1 microsecond should be expressed in JSON format as "3.000001s". - `pendingActionCount` integer - `phase` 'WORKFLOW_EXECUTION_PHASE_UNSPECIFIED' | 'WORKFLOW_EXECUTION_PHASE_PENDING' | 'WORKFLOW_EXECUTION_PHASE_RUNNING' | 'WORKFLOW_EXECUTION_PHASE_STOPPING' | 'WORKFLOW_EXECUTION_PHASE_STOPPED' | 'WORKFLOW_EXECUTION_PHASE_DELETING' | 'WORKFLOW_EXECUTION_PHASE_DELETED' | 'WORKFLOW_EXECUTION_PHASE_COMPLETED' - `runningActionCount` integer - `session` string - `stoppedActionCount` integer - `warningMessage` string — WarningMessage summarises why the workflow execution is in a warning state. If this is non-empty the workflow execution is in a warning state and likely does not match the users expectations. Deprecated: Use warnings field instead for structured warning information. - `warnings` GitpodV1WorkflowError[] — Structured warnings about the workflow execution. Provides detailed warning codes and messages. - `code` 'WORKFLOW_ERROR_CODE_UNSPECIFIED' | 'WORKFLOW_ERROR_CODE_ENVIRONMENT_ERROR' | 'WORKFLOW_ERROR_CODE_AGENT_ERROR' — WorkflowErrorCode defines error codes specific to workflows. These codes help distinguish retriable vs non-retriable errors and provide actionable information to both the reconciler and the frontend. Error code ranges: - 0: Unspecified - 1-999: Reserved for future use - 1000-1999: Environment-related errors - 2000-2999: Agent-related errors - 3000-3999: Resource-related errors - `message` string — Human-readable error message. - `meta` object — Additional metadata about the error. Common keys include: - environment_id: ID of the environment - task_id: ID of the task - service_id: ID of the service - workflow_id: ID of the workflow - workflow_execution_id: ID of the workflow execution - `reason` string — Reason explaining why the error occurred. Examples: "not_found", "stopped", "deleted", "creation_failed", "start_failed" - `retry` GitpodV1WorkflowErrorRetry — Retry configuration for the error. - `retriable` boolean — Whether the error is retriable. - `retryAfter` string, regex — A Duration represents a signed, fixed-length span of time represented as a count of seconds and fractions of seconds at nanosecond resolution. It is independent of any calendar and concepts like "day" or "month". It is related to Timestamp in that the difference between two Timestamp values is a Duration and it can be added or subtracted from a Timestamp. Range is approximately +-10,000 years. # Examples Example 1: Compute Duration from two Timestamps in pseudo code. Timestamp start = ...; Timestamp end = ...; Duration duration = ...; duration.seconds = end.seconds - start.seconds; duration.nanos = end.nanos - start.nanos; if (duration.seconds < 0 && duration.nanos > 0) { duration.seconds += 1; duration.nanos -= 1000000000; } else if (duration.seconds > 0 && duration.nanos < 0) { duration.seconds -= 1; duration.nanos += 1000000000; } Example 2: Compute Timestamp from Timestamp + Duration in pseudo code. Timestamp start = ...; Duration duration = ...; Timestamp end = ...; end.seconds = start.seconds + duration.seconds; end.nanos = start.nanos + duration.nanos; if (end.nanos < 0) { end.seconds -= 1; end.nanos += 1000000000; } else if (end.nanos >= 1000000000) { end.seconds += 1; end.nanos -= 1000000000; } Example 3: Compute Duration from datetime.timedelta in Python. td = datetime.timedelta(days=3, minutes=10) duration = Duration() duration.FromTimedelta(td) # JSON Mapping In JSON format, the Duration type is encoded as a string rather than an object, where the string ends in the suffix "s" (indicating seconds) and is preceded by the number of seconds, with nanoseconds expressed as fractional seconds. For example, 3 seconds with 0 nanoseconds should be encoded in JSON format as "3s", while 3 seconds and 1 nanosecond should be expressed in JSON format as "3.000000001s", and 3 seconds and 1 microsecond should be expressed in JSON format as "3.000001s". ## Other responses - `default` — Error ## Changes > 18 revisions in range; 1 could not be searched. - **2026-04-02** `dabc0ff98cd7` — 2 info - removed the `PRINCIPAL_AGENT_EXECUTION` enum value from the `workflowExecutions/items/metadata/creator/principal` response property for the response status `200` - removed the `PRINCIPAL_AGENT_EXECUTION` enum value from the `workflowExecutions/items/metadata/executor/principal` response property for the response status `200` - **2026-02-11** `b97dcde84128` — 40 breaking, 4 warning, 11 info - the `workflowExecutions/items/spec/action/steps/items/agent/prompt` response property's maxLength was unset from `20000` for the response status `200` - the `workflowExecutions/items/spec/action/steps/items/pullRequest/branch` response property's maxLength was unset from `255` for the response status `200` - the `workflowExecutions/items/spec/action/steps/items/pullRequest/description` response property's maxLength was unset from `20000` for the response status `200` - the `workflowExecutions/items/spec/action/steps/items/pullRequest/title` response property's maxLength was unset from `500` for the response status `200` - …51 more - …earlier changes not shown [Full history](https://skmtc.dev/gitpod-io/apis/gitpod-v1/changes/gitpod.v1.WorkflowService/ListWorkflowExecutions/post.md) --- [API](https://skmtc.dev/gitpod-io/apis/gitpod-v1.md) · [All operations](https://skmtc.dev/gitpod-io/apis/gitpod-v1/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/gitpod-io/gitpod-v1/revisions/44d50c2ac284/schema)