A flow criterion written in English fails silently on a localised org

A flow was responsible for turning activated orders into billing schedules. It filtered on Status = "Activated". The org runs in French and renders that value as “Activé”. The criterion never matched, the flow never fired, and no schedule was ever created.

Nothing failed. There was no error, no flow error email, no debug log worth reading — the flow simply did not act, which is indistinguishable from a flow that acted and found nothing to do.

The general form of this trap is worth internalising: any flow criterion comparing against a displayed value is suspect on a localised org. Compare against the API name, or against a value you control.

A related one from the same org: an object renamed in the UI makes every conversation ambiguous. One production org renames the quote object entirely, so “the quote” in a meeting and Quote in the schema are not reliably the same thing.