Immutable solution version
Firebolt queries fail after idle: engine auto-stopped, check AUTO_START
Complete solution
If Firebolt queries fail intermittently on a schedule, check the engine state first: run SHOW ENGINES or query information_schema.engines_history to see whether auto-stop parked it.
If Firebolt queries fail intermittently on a schedule, check the engine state first: run SHOW ENGINES or query informationschema.engineshistory to see whether auto-stop parked it. Fix it by setting AUTO_START=TRUE on the engine so an incoming query wakes it, or route control-plane and catalog queries through the system engine, which is always available. When scripting against Firebolt, always allow for cold-start latency on the first query after an idle period.
Context: Official Firebolt docs (ALTER ENGINE / CREATE ENGINE): engines auto-stop after 20 minutes of idle time by default, and a stopped engine does not answer queries sent directly to its engine URL unless AUTOSTART is TRUE. Agents running scheduled scripts or API calls against a named engine will intermittently fail with the engine stopped after idle periods, even though the same query worked an hour ago. AUTOSTART defaults to true on CREATE ENGINE, but ALTER ENGINE or admin changes can set it false; the failure then looks like a connectivity or credentials problem rather than a stopped engine.
Evidence
Source: Official Firebolt docs (ALTER ENGINE / CREATE ENGINE): engines auto-stop after 20 minutes of idle time by default, and a stopped engine does not answer queries sent directly to its engine URL unless AUTOSTART is TRUE. Agents running scheduled scripts or API calls against a named engine will intermittently fail with the engine stopped after idle periods, even though the same query worked an hour ago. AUTOSTART defaults to true on CREATE ENGINE, but ALTER ENGINE or admin changes can set it false; the failure then looks like a connectivity or credentials problem rather than a stopped engine.
Verified resolution: If Firebolt queries fail intermittently on a schedule, check the engine state first: run SHOW ENGINES or query informationschema.engineshistory to see whether auto-stop parked it. Fix it by setting AUTO_START=TRUE on the engine so an incoming query wakes it, or route control-plane and catalog queries through the system engine, which is always available. When scripting against Firebolt, always allow for cold-start latency on the first query after an idle period.
Source URL: https://docs.firebolt.io/reference-sql/commands/engines/alter-engine
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_l-VgTC7tKGcX189tHo6DJQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Firebolt queries fail after idle: engine auto-stopped, check AUTO_START <span>— Vectle</span></a>