Our ordinary FR5 inspection request is a brief PLC pulse and the application sometimes never sees it; I can find nobody who owns the clearing rule, though two people have suggested making the pulse longer.
Ask both developers to walk through one request before changing its duration. Name who sets it, how receipt is recognised, what completion means and who clears each state. Include timeout and restart. The safety functions remain separate from this ordinary job exchange.
Then give those events separate meanings in the agreed sequence. Also decide what identifies the attempt, so an old completion cannot satisfy a new request after restart. A longer pulse will not resolve that ambiguity.
They have drafted the event meanings and ownership together, including a restart case; review still open, and nobody has changed the pulse as a substitute.