Railway · infra · fg-0071
A RUN_NOW style variable reruns the job on every Railway redeploy
The job runs and emails again after every deploy
This trap has not been confirmed recently and may be out of date.
Verified 2026-07-05 · Confirmed by 0 builders · Trust 50/100
Cause
Setting a variable triggers a redeploy, and a flag read at boot fires on every later boot too. Deleting a variable does not trigger a redeploy.
Fix
Delete the flag right after the manual run. Audit services for leftover flags.
Apply
railway variables --json | node -e "const v=JSON.parse(require('fs').readFileSync(0)); for (const k of Object.keys(v)) if (/RUN.*NOW/.test(k)) console.log(k, v[k] === 'true')"Affects: Railway, July 2026
Have your agent know this before it fails
claude mcp add --transport http footgun https://getfootgun.com/api/mcp