Skip to main content

Sync Back Troubleshooting

Use this guide when sync back does not move documentation to your target, when Git branches look stale, when a Coalesce Transform request seems idle, when warehouse or BI metadata still looks old after a successful run, or when you need to pause sync back during a content freeze.

For destination setup and prerequisites, start on Sync Back and open the guide for your target from the comparison table.

You Requested Sync Back but Documentation Has Not Moved Yet​

Jobs queue behind other automation and may wait for validation steps inside Catalog or Git hosts.

Resolution:

  1. Open the destination-specific guide linked from Sync Back and confirm prerequisites such as tokens, branches, and roles.
  2. Allow enough time for scheduled automation before assuming failure. Many teams batch pushes nightly.

Git-Hosted Destinations Show an Older Branch Than Your Latest Catalog Edits​

Branches sometimes refresh only after upstream merges complete or when scheduled extractors rerun.

Resolution:

  1. Confirm no pending merge conflicts exist on the repository Catalog pushes to.
  2. Trigger another sync after large documentation edits so the pipeline captures the newest revision.

First Sync Back From Catalog to Coalesce Transform Seems Idle​

Professional services or operations teams may monitor these requests manually during onboarding.

Resolution:

  1. Reply to any confirmation thread from your rollout team with timestamps if nothing moves within the agreed SLA.
  2. Escalate through Coalesce Support when deadlines slip without status updates.

Warehouse-Native Sync Writes Succeed in Logs but BI Tools Still Show Old Descriptions​

Some targets cache metadata locally until their native refresh cycle runs.

Resolution:

  1. Force a refresh or republish inside the BI tool after Catalog reports success.
  2. Re-read the guide for your beta destination, such as Looker (beta), Tableau (beta), or BigQuery (beta), when APIs remain in staged rollout.

You Need to Pause Sync Back During Content Freezes​

Automation hooks continue until disabled at the source.

Resolution:

  1. Work with your Catalog administrator to disable schedules or tokens during freeze windows.
  2. Document restart steps before re-enabling pushes.