Why is a component workflow in a Pending state?

QUESTION

Why is a component workflow in a Pending state?

ANSWER

You probably have another workflow running. Workflows are currently single-threaded by design, to prevent collision.

Go into the install's workflow view in the dashboard, and cancel the other workflow that is still executing.

In this example, a Helm deployment has a pod in CrashLoopBackoff status, so after fixing the component and attempting to redeploy, it is pending until you cancel the failing component.

Components do have timeouts so eventual this would have failed, allowing the next workflow to execute.