Known issues for Workflows

Stay organized with collections Save and categorize content based on your preferences.

This page lists known issues for Workflows.

You can also check for existing issues or open new issues in the public issue trackers.

Placement of for directly after try

Placing for directly after try causes an error. For example, a single step can be placed directly after try, like this:

  - try:
      try:
        call: sys.log
        args:
          data: works
      retry: ${http.default_retry}

However, if you position for after the try, the step fails, and you cannot deploy the workflow. For example:

  - try:
      try:
        for:
          value: v
          range: [1,2]
          steps:
            - log:
                call: sys.log
                args:
                  data: ${v}
      retry: ${http.default_retry}

The error message is as follows:

Could not deploy workflow: failed to build: error in step try: loop step name should not be empty (Code: 3)

The workaround is to add a named step after the try. For example:

  - try:
      try:
        steps:
          - loopStep:
              for:
                value: v
                range: [1,2]
                steps:
                  - log:
                      call: sys.log
                      args:
                        data: ${v}
      retry: ${http.default_retry}

Events larger than the maximum arguments size

If using Workflows as a destination for an Eventarc trigger, events larger than the maximum Workflows arguments size will fail to trigger workflow executions. For more information, see Quotas and limits.

What's next

Learn strategies helpful when troubleshooting issues.