[CR-004] Server — TASKS_ENABLED kill switch (no notification storm on resume) #4

New Issue

admin · 2026-05-06T00:53:25Z

admin commented

2026-05-06 00:53:25 +00:00

Change Request

Type: Server Deploy · Risk: Low
Service: push-backend (Railway)
Date: 2026-05-05
Commit: 90f826f

Description

Added TASKS_ENABLED env var. When false, due tasks call finalizeTaskRun() (advances next_run without executing) so re-enabling does not burst all overdue tasks at once.

Self-Review Checklist

finalizeTaskRun() handles both once and recurring task types
Deployment logs clean

Rollback

git revert 90f826f && git push && railway up --detach

Status: Completed ✅

## Change Request **Type:** Server Deploy · **Risk:** Low **Service:** push-backend (Railway) **Date:** 2026-05-05 **Commit:** 90f826f ### Description Added `TASKS_ENABLED` env var. When `false`, due tasks call `finalizeTaskRun()` (advances `next_run` without executing) so re-enabling does not burst all overdue tasks at once. ### Self-Review Checklist - [x] `finalizeTaskRun()` handles both `once` and `recurring` task types - [x] Deployment logs clean ### Rollback ``` git revert 90f826f && git push && railway up --detach ``` **Status:** Completed ✅

admin added the server-deploy risk:low labels 2026-05-06 00:53:25 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: admin/1ai-ops#4