ServiceTitan Sync Issues
ServiceTitan is the system of record for jobs and estimates once they leave YND OS — YND OS pushes data outbound to it. This page covers why a push can fail and the current known blocker.
Known, currently-blocked issue: "Door / slab" material
Warning: Pushes for the Door / slab material bucket are currently blocked. ServiceTitan SKU 39723877, which this bucket mapped to, was deleted on the ServiceTitan side. Until an active replacement SKU is mapped, any push that includes a Door/slab line item will fail.
This is a known gap, not a new bug — if you hit it, you don't need to re-report the root cause, but you should still flag the specific job so it can be prioritized once a replacement SKU is mapped.
Where the mapping lives: /admin/servicetitan-mapping — this is where an admin maps YND OS material buckets to active ServiceTitan SKUs. This page is currently ungated (not restricted by role — see /help/permissions/known-gaps), so if you can see it and have context, you can check the current mapping, but only someone with ServiceTitan admin access should actually change it.
General troubleshooting steps for a failed sync
- Identify what failed. Note the job/opportunity, which material bucket(s) it includes, and roughly when the push was attempted.
- Check if it's the Door/slab issue. If the job includes a Door/slab item, that's very likely the cause — see above.
- Check
/admin/integrations/servicetitan. This is the ServiceTitan Integration admin page (visible toadminandexecutive) — it shows connection/integration status. - Check for other unmapped materials. The Door/slab SKU deletion is the known case, but any material bucket without an active mapped SKU will fail the same way. If a different bucket starts failing, treat it the same way: check
/admin/servicetitan-mappingfor a missing/inactive SKU. - Don't manually re-key the job directly in ServiceTitan as a workaround without checking with a manager first — YND OS is meant to be the source of truth going in, and manual edits on the ServiceTitan side can cause the two systems to disagree later.
What "pushed outbound" means for your day-to-day work
- Estimates and jobs are built and finalized in YND OS first.
- ServiceTitan sync failures don't block you from continuing to work the deal in YND OS — the opportunity, proposal, and payment flows are independent of whether the ServiceTitan push has succeeded.
- However, if the job can't reach ServiceTitan, downstream operations that rely on ServiceTitan (scheduling crews, invoicing through that system, etc.) will be affected. Flag it early rather than letting it surface later as a scheduling problem.
Escalation
If you hit a sync failure that isn't the known Door/slab issue, note the job ID/opportunity, the material involved, and the approximate time, and send it to an admin or manager who can check the integration page and mapping. Don't assume it's the same known issue without checking which material is involved.
Related
/help/permissions/known-gaps/help/rollout/open-decisions