Set TASKS_ENABLED=false in Railway environment. Tasks skip execution but next_run advances so schedule resumes cleanly on re-enable. Pausing to measure API cost baseline without scheduled task traffic.
Self-Review Checklist
CR-004 (kill switch code) already live
railway variables confirms value set
Deployment logs clean after railway up
Rollback
railway variables --set "TASKS_ENABLED=true" && railway up --detach
Status: Completed ✅
## Change Request
**Type:** Config Change · **Risk:** Low
**Service:** push-backend (Railway)
**Date:** 2026-05-05
### Description
Set `TASKS_ENABLED=false` in Railway environment. Tasks skip execution but `next_run` advances so schedule resumes cleanly on re-enable. Pausing to measure API cost baseline without scheduled task traffic.
### Self-Review Checklist
- [x] CR-004 (kill switch code) already live
- [x] `railway variables` confirms value set
- [x] Deployment logs clean after `railway up`
### Rollback
```
railway variables --set "TASKS_ENABLED=true" && railway up --detach
```
**Status:** Completed ✅
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Change Request
Type: Config Change · Risk: Low
Service: push-backend (Railway)
Date: 2026-05-05
Description
Set
TASKS_ENABLED=falsein Railway environment. Tasks skip execution butnext_runadvances so schedule resumes cleanly on re-enable. Pausing to measure API cost baseline without scheduled task traffic.Self-Review Checklist
railway variablesconfirms value setrailway upRollback
Status: Completed ✅