Choose the symptom you can observe
Open the matching case. Check the existing state before changing a record or repeating an action.
A row is rejected because the quantity is blank, invalid, or out of range.
Check first
- Confirm whether blank, zero, and positive values have different meanings for this rule.
- Check the entered value's number format, sign, decimal precision, and allowed range.
- Compare the row with the source count and the unit label configured for the rule.
Next action
Correct the value from the source or explicitly record why a blank or zero is intended. Keep the invalid row out of finalization until the validation message is resolved.
Confirm the result
The row passes validation, displays the intended source quantity, and appears as eligible in the next preview.
The workspace says a row is stale after someone else edited it.
Check first
- Record the franchise, rule, period, and stale-row message before refreshing.
- Compare the current row value and editor with the value originally loaded.
- Check whether the other edit changed the quantity, assignment, or period state.
Next action
Reload the current row, reconcile it with the source, and apply a new correction only if the intended value still differs. Do not force a stale write or copy the old value over a newer edit.
Confirm the result
The next save references the current row version and the history identifies both the earlier edit and the final reviewer.
Expected franchises are missing from the batch.
Check first
- Confirm the selected rule, cycle, organization, and franchise assignment filters.
- Check whether the missing franchise is inactive, unassigned, or already finalized for the period.
- Compare the assigned franchise list with the rule's current assignment policy.
Next action
Correct the rule or assignment scope through its owning workflow, then reopen the batch for the same period. Do not add an out-of-scope row manually just to make the count look complete.
Confirm the result
The batch lists the expected assigned franchises once and explains any intentionally excluded or already finalized record.
The preview total differs from the quantities just entered.
Check first
- Compare the preview timestamp with the latest row save or validation result.
- Check whether the preview excludes invalid, stale, deferred, or inactive rows.
- Recalculate the visible eligible quantities using the selected rule and period.
Next action
Resolve any excluded row and rerun the preview from the same rule and cycle. Treat deferred or blocked rows separately rather than changing quantities to force the expected total.
Confirm the result
The preview lists eligible and excluded rows, and its total can be reproduced from the latest saved quantities and rule version.
Prepare a useful escalation
- Include the rule, cycle, franchise row, source quantity, exact validation or stale message, and latest editor.
- Keep the original batch and source count when a concurrent edit or period correction is involved.
- Ask the batch owner to approve any correction that changes a finalized or previously reviewed row.
Reference the relevant record instead of copying credentials or unrelated personal information into the handoff.