remove backoff logic

Author: icecrasher321

apps/sim/background/schedule-execution.ts

@@ -39,7 +39,6 @@ import {
   SCHEDULE_INFRA_RETRY_BASE_MS,
   SCHEDULE_INFRA_RETRY_MAX_ATTEMPTS,
   SCHEDULE_INFRA_RETRY_MAX_MS,
-  SCHEDULE_USAGE_LIMIT_BACKOFF_MS,
 } from '@/lib/workflows/schedules/execution-limits'
 import {
   type BlockState,
@@ -794,20 +793,16 @@ export async function executeScheduleJob(payload: ScheduleExecutionPayload) {
 
           case 402: {
             /**
-             * Usage limits are a billing state, not a broken workflow, and only clear
-             * on billing-period rollover or upgrade. Back off to at most the usage-limit
-             * cadence (never faster than the schedule's own cadence) so an over-limit
-             * schedule stops re-running every tick, and count each hit toward the shared
-             * auto-disable threshold so an abandoned over-limit schedule eventually stops.
+             * Usage limits are a billing state, not a broken workflow, but they only
+             * clear on billing-period rollover or upgrade. Keep retrying at the normal
+             * cadence, but count each hit toward the shared auto-disable threshold so an
+             * abandoned over-limit schedule eventually stops instead of running forever.
              * A successful run resets failedCount, so transient overages self-heal.
              */
-            const cronNextRunAt = await calculateNextRunFromDeployment(payload, requestId)
-            const backoffRunAt = new Date(now.getTime() + SCHEDULE_USAGE_LIMIT_BACKOFF_MS)
             const nextRunAt =
-              cronNextRunAt && cronNextRunAt.getTime() > backoffRunAt.getTime()
-                ? cronNextRunAt
-                : backoffRunAt
-            logger.warn(`[${requestId}] Usage limit exceeded, backing off scheduled run`, {
+              (await calculateNextRunFromDeployment(payload, requestId)) ??
+              new Date(now.getTime() + 60 * 60 * 1000)
+            logger.warn(`[${requestId}] Usage limit exceeded, counting as failed run`, {
               scheduleId: payload.scheduleId,
               nextRunAt: nextRunAt.toISOString(),
             })

apps/sim/lib/core/config/env.ts

@@ -204,7 +204,6 @@ export const env = createEnv({
     SCHEDULE_INFRA_RETRY_BASE_MS:          z.string().optional().default('60000'),
     SCHEDULE_INFRA_RETRY_MAX_MS:           z.string().optional().default('300000'),
     SCHEDULE_INFRA_RETRY_MAX_ATTEMPTS:     z.string().optional().default('10'),
-    SCHEDULE_USAGE_LIMIT_BACKOFF_MS:       z.string().optional().default('3600000'), // Min gap between retries while over usage limit (default 1h)
 
     // Cloud Storage - AWS S3
     AWS_REGION:                            z.string().optional(),                  // AWS region for S3 buckets

apps/sim/lib/workflows/schedules/execution-limits.ts

@@ -40,14 +40,3 @@ export const SCHEDULE_INFRA_RETRY_MAX_ATTEMPTS = envNumber(
     integer: true,
   }
 )
-
-/**
- * Minimum delay before a schedule retries after hitting a usage limit (402).
- * Usage limits only clear on billing-period rollover or upgrade, so over-limit
- * schedules back off to (at most) this cadence instead of re-running every tick.
- */
-export const SCHEDULE_USAGE_LIMIT_BACKOFF_MS = envNumber(
-  env.SCHEDULE_USAGE_LIMIT_BACKOFF_MS,
-  60 * 60_000,
-  { min: 1, integer: true }
-)