KamoCRM

Trainer must not clobber its own claim or an operator's pause

FixSecurityService
Shipped
15 ஜூலை, 2026 அன்று 3:29 AM UTC
Author
Kamo
Commit
37b266d

After the atomic claim() bulk-updates the row to RUNNING, mirror that in the in-memory entity — the pool thread has no open session, so a later full-row save would otherwise merge the pre-claim status back and undo the lock. In-loop progress now goes through the status-preserving saveProgress(); a 0-row result means the run was paused or reclaimed, so the walk stops and leaves that status in place.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing