A screen flow collects information from a person and uses it in a defined process. Screen fields are inputs; later decisions and record actions must use the supplied values. A canvas can pause at a screen until those inputs exist. That pause is different from a failed record update.
Give each element a clear label and check its connector. A field visible on a screen doesn't automatically save itself to a record. The flow needs an appropriate assignment or record action, and its execution context still matters. Test a missing input, a valid response, and a different record identity. This simulator's Debug input panel supplies the screen values explicitly so you can inspect both the pause and the completed trace.