If the page says an import decision could not be confirmed, reload the same saved import before continuing. The server may have received the decision even though your browser did not receive a usable result.
- Keep the company, batch and source file identifiable. Do not start a new upload of the same rows.
- Open the saved import from Import history and wait for its current rows and counts to load.
- Inspect the affected decisions and resume only from the current saved state.
A stale browser display can show an earlier undecided count. Reading the current batch prevents an unnecessary second decision or a mistaken assumption that nothing saved.
Check your current workspace
If you changed company or signed-in identity while the request was running, return to the authorized scope for that batch. Do not treat a different company’s empty list as evidence that the original import disappeared.
If the current saved state still cannot load, report the filename, account, approximate decision time and exact error. Keep source amounts unchanged while recovery is investigated. Once the result is clear, review the eligible count before committing the batch.
Was this article helpful?
Tell us whether this answered the question you came with.