The FR5 package's current waiting step names the old receiving fixture even though the installed job is for its replacement; I've kept both package identities and the matched event history, and want support to explain which branch supplies that wait before another generic video request.
Check which configuration the normal launcher actually loads. A new job name can sit above an old fixture mapping. Have the package author compare the loaded path and active branch.
Normal launcher loads the new job file but the old fixture configuration from a shared folder, according to the startup record; the maintainer has sent both resolved paths to the author
Old input mapping, not just the label; its expected receiving confirmation belongs to the removed fixture, and the installed fixture drawing identifies a different input
Ask the author to explain why the old file was found. A corrected mapping is useful, but somebody restoring the same backup can put it straight back. We need a job package which brings its intended configuration with it, not a workstation which happens to contain the right leftovers.
The installation check used the author's direct launch from the new package folder; the normal shortcut retained the shared configuration location, which is now part of the correction
That explains why it looked intermittent across users. Were all your reported stops started through that shortcut, though? I'd keep any direct-launch failures separate until checked.
The retained failures in this ticket all have the normal shortcut's startup path; I've left an older unrecorded complaint outside that conclusion rather than assigning it the same cause
And reject the wrong fixture identity if somebody selects that old file deliberately. A file existing isn't enough to make its input names belong to the installed tooling.
The revision requires its intended fixture identity and reports a missing or mismatched configuration instead of falling back; the maintainer is checking that plus the receiver-available and receiver-unavailable cases from the normal shortcut
The package author updated them, and maintenance restored the package and repeated the normal-shortcut checks, including missing and wrong configuration cases; the receiver states now match the installed fixture and this ticket's mapping fault is closed
Thanks for reporting the restore check. Send the seller that corrected package identity with closure, so another contact doesn't offer you the old shared-folder version again.