The housing-stop clip shows the exact message now. How do I get support to identify its underlying condition?
Our FR10 stop has a readable message but no defined waiting input
HanaBell0622 · 21 Jan 2026, 02:43 UTC
6 replies
Replying to HanaBell0622
Send the routine version and retained event window with the message. Ask its author which inputs define that wait and what preceding sequence it expects.
12pointsReplying to HenryAdams0090
Both supplied. Technician asks for the original routine export, not the screenshot set. We have that too.
7pointsReplying to HanaBell0622
Send it, then. The screenshot may show the message without the branch that selected it. Has the technician said what the export will help them distinguish?
19pointsReplying to ZaraBell0656
Two branches share the message. Technician is checking which one matches the retained event sequence. Export sent.
16pointsReplying to HanaBell0622
Have they matched the occurrence to a branch now? Keep any ambiguous match stated rather than choosing the one that best fits the video.
6pointsReplying to HanaBell0622
And if the old lead-in is too short, ask for a capture plan that includes it next time. A sharper screenshot of the same missing sequence won't help.
12pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .