75 Release Notes
New AwaitingCloudQuota backend status
For Cloud Life Sciences v2beta only.
When a user's GCP project reaches a quota limit, Cromwell continues to submit jobs and Life Sciences acknowledges them as created even if the physical VM cannot yet start. Cromwell now detects this condition in the backend and reports AwaitingCloudQuota.
The status is informational and does not require any action. Users wishing to maximize throughput can use AwaitingCloudQuota as an indication they should check quota in Cloud Console and request a quota increase from GCP.
AwaitingCloudQuota will appear between the Initializing and Running backend statuses, and will be skipped if not applicable.
Now:
| Status in metadata | Quota normal | Quota delay | Status meaning |
|---|---|---|---|
executionStatus
| Running
| Running
| Job state Cromwell is requesting from the backend |
backendStatus
| Running
| AwaitingCloudQuota
| Job state reported by backend |
Previously:
| Status in metadata | Quota normal | Quota delay | Status meaning |
|---|---|---|---|
executionStatus
| Running
| Running
| Job state Cromwell is requesting from the backend |
backendStatus
| Running
| Running
| Job state reported by backend |
New 'requestedWorkflowId' API Option
Allows users to choose their own workflow IDs at workflow submission time.
If supplied for single workflows, this value must be a JSON string containing a valid, and not already used, UUID. For batch submissions, this value must be a JSON array of valid UUIDs.
If not supplied, the behavior is as today: Cromwell will generate a random workflow ID for every workflow submitted.
Bug Fixes
- Fixed a bug on Google Pipelines API backends where missing optional output files (
File?) were not correctly detected by Cromwell and caused invalid call cache entries to be written.