A business user reports that an OmniScript 'stopped working' after a release. How do you approach the diagnosis?

Resist the temptation to open the designer first; establish what actually changed and for whom.

1. Scope it: one user or everyone, one record or all records, one Step or the whole script. The answer usually eliminates most of the possible causes immediately.
2. Check the active version. A release may have activated a new version, or deployed one and failed to activate it. Compare what is active against what was expected.
3. Check dependencies. An Integration Procedure or Data Mapper the script relies on may have been changed, deactivated, or deployed without its own dependencies. A script that 'stopped working' is frequently a downstream component that changed.
4. Check permissions and data. If it fails for one persona only, look at object and field access and at record sharing before looking at logic.
5. Reproduce with preview and the debug tools, watching the data JSON build up and inspecting each action's request and response, so you can point at the exact element rather than guessing.
6. Then look at what shipped. With the failure localised, the release diff for that component usually shows the cause in seconds. Doing this step first, before scoping, is how a fifteen-minute fix becomes an afternoon.