Back end is full of hidden workflows

Why is 'workflow' something special? Most/all code is workflows; there are many 70s programming books that show all code as workflow diagrams. How is it hidden? Or did we, as often is the case, change the definition? Not according to Google/Gemini anyway.

are people really writing workflows without knowing it?

or just making tradeoffs that its not complicated enough to need a workflow yet, then have troubles scheduling the move once it gets more complicated?