DATAAPI-46: skip queue flag updates#96
Merged
DominicWatson merged 2 commits intostablefrom Mar 16, 2026
Merged
Conversation
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.
Note
Medium Risk
Changes the conditions under which insert/update/delete operations are enqueued, which can alter downstream sync/queue behavior if the flags are set or interpreted differently.
Overview
Refactors
DataApiInterceptors.cfcto centralize all “should we queue?” checks into a new_skipQueue(interceptData)helper, replacing duplicated per-handler logic.This makes
skipDataApiQueueand theskipSyncQueue→API-queue bypass behavior consistent acrosspostInsertObjectData,postUpdateObjectData, andpostDeleteObjectData, while still short-circuiting when the application is not yet loaded.Written by Cursor Bugbot for commit f792c6c. This will update automatically on new commits. Configure here.