Mapper: an Auto Match run keeps going after you leave the project

Leaving a project while Auto Match is still running (for example, going to the project list) unmounts MapProject, but nothing stops the run. abortRef is set only by Stop and by a 403.

The run keeps spending match operations and AI calls.
Its state updates are dropped, but it keeps writing refs (candidates, row logs). When it finishes, it schedules an autosave (scheduleAutoSave('auto_match')) on the page's leftover scheduler. That save combines state frozen at unmount (matches, decisions, analysis) with the live refs, so the stored project is inconsistent.
Decide the behavior: stop the run when the user leaves (set abortRef on unmount, perhaps after a confirm), or keep it running and save its results consistently.
Either way, nothing spends quota after the user leaves unless we mean it to.

Found in review of OpenConceptLab/oclmap#75 (#2829). It predates that PR.

🤖 Generated with Claude Code

Automated Triage — 2026-09-28

Dimension	Score
Complexity	3
Scope	2
Clarity	3
Dependency	2
Risk	3

Decision: decision/human-review
Type: type/bug
Signals: signal/small-scope

Fixing this requires deciding whether to abort the run on unmount or make its completion save consistent, and then wiring that into MapProject.jsx and autosave.js — a few files but no unresolved external blocker since #75/#2829 already merged. Clarity is middling because the behavior decision is explicitly left open; risk is moderate since an unbounded run wastes AI quota and can leave stored project state inconsistent, but it isn't a data-loss or security issue.

Generated by ticket-triage pipeline v3. Model: anthropic/claude-sonnet-5 (openrouter).

I think we should show a dialog that automatch is running do you want to leave? with "abort and leave" and "Stay" actions.
And on unmount we should abort immideatly (current abort waits for graceful stop) and record the automatch run

OpenConceptLab/ocl_issues#2830 | stop and save the run on Stop and le…

Update: fixed in two PRs.

OpenConceptLab/ocl_issues#2830 | stop Auto Match when leaving the project oclmap#114 (Mapper)
- Leaving a project while Auto Match runs asks Stay or Stop and leave. Closing or reloading the tab shows the browser's prompt.
- Leaving stops the run at once instead of gracefully. Its record is closed as stopped right away, what it matched so far is saved, and no autosave runs after the page is gone. No new requests go out after leaving.
- Closing the tab also stops the run and closes its record, with a keepalive request.
OpenConceptLab/ocl_issues#2830 | expire Auto Match runs left running for over 24 hours oclapi2#960 (API)
- Covers the one case the Mapper can't: the tab closes while the run's create request is in flight, so the client never gets the run id. An hourly task cancels runs left running with no update for 24 hours.

Still true: requests already sent when the user leaves still finish on the server. Their results are dropped.

🤖 Generated with Claude Code

OpenConceptLab/ocl_issues#2830 | remount the page for another project…

OpenConceptLab/ocl_issues#2830 | give Back and Forward a new page, ke…

OpenConceptLab/ocl_issues#2830 | send nothing after leaving, build th…

Merge pull request #114 from OpenConceptLab/issues#2830

OpenConceptLab/ocl_issues#2830 | expire Auto Match runs left running …

Navigation Menu

Repository navigation

Mapper: an Auto Match run keeps going after you leave the project #2830

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Mapper: an Auto Match run keeps going after you leave the project #2830

Description

Activity

ocl-automation commented on Sep 28, 2026

snyaggarwal commented on Oct 6, 2026

snyaggarwal commented on Oct 26, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions