Undo an import you did not mean to run

The wrong file, the wrong week, the wrong network: it is the first-month mistake, and it is reversible. Every import has an undo.

The one rule

Every row of this import that you have not decided on is deleted. Every row you already decided on stays.

That is the whole rule, and the screen says it in the same words. Undecided rows go, with the flags raised on them. Decided rows stay, with your decision, because a decision is a record of something you did — deleting it to tidy up an import would be the more surprising behaviour.

How to undo an import

1. Open Imports and click the import in the list — network, day, rows, matched, flagged, who ran it.
2. On the import's page, read the undo card. It tells you exactly how many rows would be deleted and how many would be kept.
3. Confirm.

Everything happens in one database transaction: the undecided rows are deleted, what remains is counted, and the import record itself is removed last so the kept rows simply lose their link to it. The undo is written to the workspace's audit log in the same transaction — which import, who ran it, how many rows went and how many stayed — so it can be answered later even though there is no screen for it yet.

The typed confirmation

Above 100 rows you are asked to type a phrase, delete 412 rows, with the real number in it. The box is a courtesy; the server counts the rows again and checks the phrase again, so a browser that skips it is refused.

The threshold counts the rows that would go, not the rows the import brought in. An import of 5,000 rows where you have already decided nearly everything is a small undo, and is treated as one.

What happens to the review queue

The rules are re-run straight after, so the queue's totals fall to match. Flags on deleted rows are gone with them; decisions you kept are untouched. Give it a few seconds and refresh.

When undo is not the answer

• You imported the right file with the wrong columns mapped. Undo it, then import again — the mapping question comes back when the header layout is one AffCheck has not saved an answer for.
• You imported the same file twice. Nothing to undo: rows de-duplicate on the transaction id, or on the order reference and date when there is no id, so the second import updated rows instead of adding them.
• You want the whole store gone. That is a different action, with a different warning: delete your data or your workspace.
• The import failed. A failed import has nothing to take back; see when an import fails or gets stuck.