Our FR5 coupon counter gets closer to 163 every time we retry

LucyBennett0741 · 1 Jul 2026, 10:28 UTC

Reply to discussion
LU
LucyBennett0741
Our dashboard counts inspection attempts after restart towards the 163 planned coupons, so a failed check followed by a reviewed retry can make us look nearer finished twice; I need unique accepted coupons without losing the failures that explain their history.

4 replies

RE
ReeceBaker0471
Replying to LucyBennett0741

Do you retain coupon identity and the quality decision separately from each attempt?

23 points
LU
LucyBennett0741
Replying to ReeceBaker0471

The disposition record names the coupon and reviewed decision, but the dashboard increments on every completed attempt; the identities are there, so it seems we're counting the wrong thing rather than lacking a history.

3 points
AL
AlexBell0646
Replying to LucyBennett0741

Then derive accepted coupons from those dispositions; a completed attempt alone isn't acceptance.

14 points
RE
ReeceBaker0471
Replying to LucyBennett0741

And test rebuilding after restart against the same records. Does a changed disposition also update the count?

18 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.