Drift compares each assigned client account’s current configuration to its assigned blueprint version. It checks configuration, not record values.
Run a check
- Open Drift and choose Check for one assignment.
- Choose Check all to queue checks for every assignment.
- Pro and Enterprise can schedule checks daily or weekly from Settings.
- Core supports manual checks.
What is checked
- Custom objects: missing objects, labels, descriptions, primary display, and searchable properties
- Custom-object capacity
- Standard objects: missing standard objects are blocked because GridLane cannot create them
- Fields: missing fields, type differences, name, required flags, section, and options
- Sections and field placement
- Associations: missing definitions and label/type differences
- GridLane views: missing, changed configuration, sharing/default state, and template ownership
- GridLane permissions: missing rules, changed flags, and ownership conflicts
What is not checked
- Record values or record counts
- Live association links between records
- Workflows, pipelines, calendars, forms, campaigns, tags, or other HighLevel assets
- Whether a field is being used by a customer
Statuses
| Status | Meaning |
|---|---|
| Compliant | No missing or changed configuration and no conflicts |
| Drift | Something needs to be created or updated |
| Blocked | A conflict or limit requires manual action |
| Pending | The check has not run yet |
| Failed | The check itself failed |
Local-only fields and other extras are reported as local-only and do not make a location non-compliant. GridLane never deletes them.
Review the differences
Open the difference list on a drift row or in a drift job to see the exact actions:
- Create — the blueprint item is missing
- Update — the target differs from the blueprint
- Blocked — GridLane will not change the target automatically
- Local only — the target has an extra local item
If a blueprint adds a field to the source but the target is still assigned to an older blueprint version, the old version does not include that field. Recapture or update the assignment before expecting the new field to appear in drift.
Apply a fix
Choose Apply on a drifted assignment to queue an add-only deployment for that location. A blocked item requires manual resolution first, such as changing a field type, deleting a conflicting local rule, or freeing custom-object capacity.
A successful apply can make the location compliant, but it does not override existing field definitions.
Metadata fast path
When the location’s object timestamps and view/permission configuration hash have not changed since a recent full check, GridLane can reuse the previous result instead of recapturing everything. The check still reports the last known status and details.