Replit Auto-Termination Policy Transition for Free-Tier Repls

Replit's idle-termination behavior establishes a compatibility boundary for Repls that require execution windows beyond the default limits. Free-tier Repls are automatically shut down after a period of inactivity, while the criteria for exemption on paid plans are not publicly documented. This boundary impacts workloads that depend on continuous state or long-running service endpoints, as the process is terminated without a graceful shutdown signal. Users cannot query the active timeout value nor register cleanup handlers before termination occurs.

What criteria determine whether a paid Repl qualifies for long-running exemption? Examine how termination boundaries differ across Repl subscription tiers? Explore whether a configurable or queryable timeout mechanism can be introduced without disrupting existing workflows?