Which ShotGrid Toolkit root path definitions cause local success but production failure?

Problem Context

The ShotGrid Toolkit is often configured on a developer’s workstation with absolute or OS‑specific paths in the roots section of templates.yml or the site preferences. Those paths resolve correctly on the local machine but may not exist or be mounted on production render farms or other OSes.

Unresolved Decision

When the same configuration is deployed to a distributed environment, users receive a cached copy of the YAML files. If a root path is missing or mismatched on a production host, the Toolkit bootstrap silently falls back to a default or an alternate environment, leading to silent failures or incorrect asset resolution.

Goal

Identify a configuration strategy that guarantees consistent root path resolution across both local development and production render environments, accounting for OS differences and distributed cache behavior.

Questions

• Which root path definitions should be used to guarantee consistent resolution across local and production environments?
• How can we detect mismatched root definitions before deployment?
• What testing strategy ensures that a distributed configuration receives updated root definitions after a change?