Why does reconnect add another accepted plate without another FR5 result?

ZaraBell0656 · 17 Mar 2026, 06:30 UTC

Reply to discussion
ZA
ZaraBell0656
Our FR5 monitor reconnects, sees the retained completion and adds another accepted plate. No new check happened. I want the maintainer to match that state to its existing job instead of clearing it or sending again.

3 replies

SA
SarahCarter1024
Replying to ZaraBell0656

Does the retained data identify the completed attempt, and does your saved history already contain it? Start there before deciding whether this is an unseen result or a repeat of one you counted earlier.

7 points
ZA
ZaraBell0656
Replying to SarahCarter1024

It carries the attempt identity, and that exact result is already saved. Reconnect was treating a true completion as a new event. Maintainer's revised replay leaves the result and accepted count unchanged; installed checks still pending.

15 points
SA
SarahCarter1024
Replying to ZaraBell0656

Keep an unseen completed attempt and an unidentified retained result in those checks too. Your known duplicate has a clear answer; the monitor must not silently discard everything it encounters after reconnect just to stop the double count.

9 points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.