a month ago
Hi,
All of our infisical secret syncs with Railway, across all services, are failing. I reached out to Infisical, but then I noticed when I manually attempted to update my secrets, it was not responding to that either. After a few hours, those secrets appeared, and I don't know if that was due to secret syncing or my manual intervention.
Is there something going on with Railway's service for secret management to have issues? Thanks.
1 Replies
Status changed to Open Railway • about 1 month ago
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
I might be seeing something similar.
One thing that stands out is that the updates don't appear to be failing permanently—they eventually show up hours later. That makes me wonder if the issue is somewhere in the sync/event processing path rather than the actual secret storage layer.
When I see behavior like this, it's usually one of:
- webhook delivery retries
- a backlog in the sync worker/queue
- delayed cache invalidation
- propagation issues between projects/environments
It would be useful to know whether Railway is receiving the Infisical update events immediately and whether those events are being processed in real time.
A quick test could be:
- Create a new secret in Infisical.
- Record the exact timestamp.
- Check when the value appears in Railway Variables.
- Check when the running container actually sees the updated environment variable.
If the timestamps differ significantly, that should help narrow down where the delay is occurring.