A reusable flow needs an explicit contract. The calling flow supplies input values and receives output values; a similar field name alone does not connect them. Keep the called flow active and choose an autolaunched flow for background work. This workspace limits reusable calls to the same record object and an after-save caller.
Inspect the call trace before trusting the resulting flag. Missing input mappings can turn a valid output blank, while a missing output mapping leaves the caller unchanged. Test true and false inputs rather than fixing a result for one example. A recursive call can repeat forever, so the runtime rejects call cycles and caps nesting. These local checks do not measure production limits or release permissions.