Repository navigation
docs(entities): document concurrency behavior of bulk methods - #348
Merged
Merged
Conversation
Add notes to updateMany(), bulkCreate(), bulkUpdate(), deleteMany(), and upsert() saying they aren't transactions, and explain how to claim a single record safely with updateMany(). Each note links to the new Concurrent updates section in Entity Schemas. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
🚀 Package Preview Available!Install this PR's preview build with npm: npm i @base44-preview/sdk@0.8.56-pr.348.9938d5fPrefer not to change any import paths? Install using npm alias so your code still imports npm i "@base44/sdk@npm:@base44-preview/sdk@0.8.56-pr.348.9938d5f"Or add it to your {
"dependencies": {
"@base44/sdk": "npm:@base44-preview/sdk@0.8.56-pr.348.9938d5f"
}
}
Preview published to npm registry — try new features instantly! |
abrahams-wix
approved these changes
Oct 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The AI chat has been telling users that concurrency "isn't documented, contact support" when they ask whether
updateMany()is atomic, whether bulk calls are transactions, or whether 2 users can claim the same record at once. That caused about 210 tickets last month. Engineering confirmed the behavior, and it's now documented in Concurrent updates. This PR adds the same facts to the SDK reference.What changes
updateMany(): each matching record is updated on its own, and the call isn't a transaction. Explains how to claim one record safely: pass itsidas a plain value plus the conditions that must still be true, then checkupdated. Notes that conditions are only rechecked at write time for a single-idquery. Adds a "Claim a record" example.bulkCreate(),bulkUpdate(),deleteMany(),upsert(): not a transaction, so if the call fails partway, records already written stay written.upsert(): concurrent calls with the same key can create duplicate records.Each note links to the Concurrent updates section. JSDoc only, no code changes.
The generated page is in base44-dev/mintlify-docs#2735.
🤖 Generated with Claude Code