You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Mapper: a stopped Auto Match run isn't autosaved, so leaving loses the rows it finished #2835
Pressing Stop during an Auto Match run leaves the rows it already finished on screen, but nothing saves them. If the user leaves or reloads without a decision or Save, those match results and AI analyses are gone, and their match operations and AI calls are already spent.
Why: the run schedules its autosave only when it wasn't stopped: if(!abortRef.current) scheduleAutoSave('auto_match') (MapProject.jsx, since #2188). Auto-proposals set decisions without scheduling a save. With nothing pending, the leave-time save from #2829 has nothing to flush, and going to the project list shows no prompt.
Decide whether a stopped run saves what it finished. The button's "Stopping gracefully" label suggests it should.
A small, well-localized fix in MapProject.jsx's autosave scheduling, but the checklist itself asks to first decide whether stopped runs should save, and explicitly says to coordinate with #2830 which is still open, so clarity and dependency aren't fully resolved. Risk is moderate since getting the interaction with #2830's abort/save logic wrong could leave inconsistent saved project state.
Generated by ticket-triage pipeline v3. Model: anthropic/claude-sonnet-5 (openrouter).
Fixed by OpenConceptLab/oclmap#86 (merged 2026-10-01, live in the Mapper since that day's 1.0.12-beta release): a run stopped with Stop now autosaves the rows it finished, as a completed run does. That PR was filed under #2849 and didn't reference this ticket, so it's closed by hand.
Activity
ocl-automation commentedon Sep 28, 2026
Automated Triage — 2026-09-28
Decision:
decision/human-reviewType:
type/bugSignals:
signal/small-scope,signal/has-dependenciesA small, well-localized fix in MapProject.jsx's autosave scheduling, but the checklist itself asks to first decide whether stopped runs should save, and explicitly says to coordinate with #2830 which is still open, so clarity and dependency aren't fully resolved. Risk is moderate since getting the interaction with #2830's abort/save logic wrong could leave inconsistent saved project state.
Generated by ticket-triage pipeline v3. Model: anthropic/claude-sonnet-5 (openrouter).
paynejd commentedon Oct 2, 2026
Fixed by OpenConceptLab/oclmap#86 (merged 2026-10-01, live in the Mapper since that day's 1.0.12-beta release): a run stopped with Stop now autosaves the rows it finished, as a completed run does. That PR was filed under #2849 and didn't reference this ticket, so it's closed by hand.