A definitively rejected reconciliation request has a different recovery path from an uncertain result. The panel offers Discard rejected request and refresh so you can clear that rejected attempt before preparing a corrected action.
- Read the rejection and identify the validation, source, or access issue.
- Use the offered discard control for the rejected request.
- Refresh the current period, resolve the issue, and prepare a new action from current evidence.
Do not discard an uncertain result as though it failed
If the message says the saved result could not be confirmed, use Retry retained request instead. That request may already have completed, so its original outcome needs to be established first.
If clearing a rejected request fails, the interface asks you to keep the browser’s saved data and try again. Do not erase storage to force the form back to an empty state while the outcome is unclear. For a rejected statement-start request, the panel offers its corresponding Discard rejected request action. After clearing, correct the actual cause rather than submitting identical invalid details. A clean new request should reflect the correct account, dates, evidence, permissions, and selected activity supported by the refreshed workspace.
Was this article helpful?
Tell us whether this answered the question you came with.