Browse this guideReprocessing a project
Customer guideUpdated 2026-10-17

Reprocessing a project

Reprocessing reads a project's earlier messages again and organizes them the way Provenience would organize them today. You see the old and new records side by side and decide whether to keep the new ones. Nothing changes until you confirm.

When to use it

Reprocess a project when its records no longer match how you would organize them now:

Only an active project can be reprocessed. Closed projects and company-level records are not reprocessed. New categories apply to new messages on their own; reprocessing is how you apply them to a project's earlier ones. See Typology.

Start, watch, and cancel

Open the project from Projects and find its reprocessing section. Reprocess project opens Reprocess this project?, which says how many messages the run would cover. Choose Start to begin, or Not now to leave it.

The run covers every message that has a current record on the project, including messages that have open cards in the Review Queue. Only one reprocess can be open for a project at a time. If one is already open, or the project is not active, the section says so instead of offering the button.

While it runs, the section shows progress, such as Reprocessing: 40 of 120 messages, with a count of any that failed. Messages are handled one at a time, oldest first. New messages that arrive meanwhile are handled normally and are not part of the run, and they always go first, so a long run never holds up your day-to-day work. A run is paused while organizing is switched off and carries on where it left off when organizing is back on, and it picks up again after any interruption.

To stop a run, choose Cancel, then Stop the rerun in Cancel the rerun?. Nothing changes; anything written so far is kept as history.

What changes and what doesn't

Your current records stay in place and visible for the whole run, and until you confirm. If you discard or cancel, they are exactly as they were.

Most carrying is automatic: when an old record maps to exactly one new record, your work simply moves across. A few cases cannot carry cleanly, such as a new record that contradicts your correction, or an old record the rerun split into several or merged into one. The review lists each one with a default:

No default ever widens access. A new record from a message you had restricted takes that restriction.

Read the review

When a run finishes, the project's section shows Finished with a link to Review the results, and a Reprocessing review card appears in the Review Queue. The review has these parts:

Your choices are not saved until you confirm. If you leave the page, you will lose them.

Confirm or discard

Confirm opens Confirm the new records?, which says how many messages' records will be replaced and which will keep their current ones. Confirming replaces the old records with the new ones for every rerun message, all together or not at all. The old records are kept as history, and your choices are applied.

Confirming changes the Review Queue:

Discard opens Discard this rerun?. It keeps the current records and throws away the rerun (kept as history). The card closes and nothing else changes.

The project's section then shows when the last reprocess was confirmed or discarded.

Based on after a reprocess

A record's Based on list follows a cited record that was replaced to its successor and marks it as updated by reprocessing. Where there is no successor, it shows the cited record as an earlier version. See Artifacts for the detail.

What it costs

Reprocessing uses the same AI allowance as new messages. A large project can use a noticeable share of it, and there is no separate allowance for reprocessing. If the allowance runs out, organizing stops for new messages as well, until it is restored.