11 days ago
For some reason a lot of my Doppler configs syncs are being automatically disabled with the connection to my production environment services. I don't know why.
On my railway dev environment - all syncs see to be fine with Doppler.
2 Replies
Status changed to Open Railway • 11 days ago
10 days ago
dev syncing fine, prod disabled = either the doppler service token authorising the prod sync got revoked/expired (90-day default), or doppler hit a sustained push failure on railway's side and auto-disabled.
quickest path:
- doppler dashboard → integrations → your railway integration → activity log for the disabled prod syncs. doppler logs the exact error it got when pushing — usually 401 (expired token), 403 (revoked), or 4xx (project/env id on railway side changed).
- if 401/403: regenerate the doppler service token used by the prod sync and reconnect on the doppler side.
- if 404 / "project not found": the railway prod project or environment was renamed/recreated since the integration was set up. delete the integration and re-add it pointing at the current prod environment.
if dev uses a separate service token / separate integration (or even a different doppler config altogether), that's why it kept working — the per-environment scoping is on the doppler side, not railway's.
6 days ago
Thanks for the info.
Apparently the Doppler bot is disabling the sync (im using the Doppler MCP and CLI)
Attachments