Gluesync Module

Validator

Compare a replicated entity with its target, see every difference, and optionally write the source values back. Schedule it with Chronos or call it from an MCP client.

Gluesync Validator comparing source and target rows

Why Validator

Know the target still matches the source

01 / Silent drift

Replication is not a proof

A pipeline can be running while rows diverge: a filtered write, a manual edit on the target, a type that did not survive the mapping.

02 / Ad-hoc SQL

Diffs that live in a spreadsheet

Comparing two databases by hand does not tell the platform, does not page a large table safely, and does not leave an audit of what was fixed.

03 / The platform outcome

One entity, one answer

Validator scans source and target in key order, stores the differences, and can reconcile them under the same permissions as the Control Plane.

Capabilities

Compare, alert, or repair

Validator is part of Gluesync 2.3. It compares one entity at a time and reports rows only on the source, rows only on the target, mismatched values, and schema differences.

Control Plane

Open it on the entity you mean

From the nav, the entity menu, or entity detail

Validate jumps straight to that pipeline and entity. Agents and the primary key come from the entity definition, so you do not re-enter connection details.

  • Source only, target only, value mismatch, and schema difference
  • Reconcile a selection or the whole run
  • Mismatched cells stay marked while the fix is applied

View Validator docs ↗

Validator
Validator run with source and target differences

Chronos

Schedule it, or fail closed

entity_validate with an optional reconcile

A Validate job checks each selected entity. Leave reconciliation off and any difference fails the job: the breakdown is the error Chronos sends by webhook and email. Turn it on and Chronos asks Core Hub to reconcile every remaining difference, failing only when a row could not be written.

  • Schedules, chained events, and trigger flows
  • At least one entity; groups are not a target
  • Platform events for started, completed, differences, failed, and reconciled

View scheduled validation ↗

MCP and API

Same comparison for agents

Six tools in the 125-tool Core Hub catalog

trigger_data_comparison needs a pipeline and an entity. reconcile_data_comparison_differences can fix every remaining difference with reconcile_all, or a list of difference ids.

  • list_data_comparison_runs and get_data_comparison_run
  • list_data_comparison_differences
  • cancel_data_comparison_run

View Core Hub MCP docs ↗

Resources

Guides, roadmap and support

Roadmap

Public Roadmap

What we're building next. Submit feature requests.

View roadmap ↗
Support

Support

Access technical support and operational assistance.

Get support ↗
Status

Service Status

Real-time platform availability and incident history.

Check status ↗

Check the target, then decide whether to fix it

Start a free trial or talk with the MOLO17 team about validation and reconciliation on your pipelines.