If the workflows section of a CircleCI config isn’t valid, running
circleci config validate -c .circleci/config.yml will still return that it’s valid. What’s worse is that the Builds section of CircleCI’s interface won’t show anything. It’s like your build doesn’t exist. If however, you go to the Workflows section it shows a nice icon that says Needs Setup with an extremely helpful message about what in the workflows section was wrong. However this isn’t clear and it took me 30-60 minutes to figure out that was the correct way to debug this…
Fortunately I found 2.0 Builds not working… which was open for a month without any activity from CircleCI staff, despite clearly demonstrating that there’s a documentation issue for this.
Either the validate functionality of the CircleCI Local CLI should be improved so that it returns the same extremely helpful message as the workflows section of the interface, or the documentation for it should be updated to warn people that it is really only validating half of the config, not the whole thing which the documentation purports to do.