Lock down ordering in workflow diagram



We have a pretty basic workflow process where we build a release, which can then be deployed on either a QA or a production environment. CircleCI creates the following diagram for it:

The diagram creation is a bit inconsistent: the order of the production and QA steps seems to be pretty random. Sometimes approve-production is shown first, and sometimes approve-qa. This makes it very easy accidentally click the wrong thing. Can the order be locked down so it never changes? Preferably to use the same order as used in config.yml ?


Plus ONe for this one.