apache/superset · error · TemporaryCacheGetFailedError
An error occurred while accessing the value.
Error message
An error occurred while accessing the value.
What it means
TemporaryCacheGetFailedError is raised by the explore form_data get command when reading or refreshing the cached state raises SQLAlchemyError — the except wraps the cache get, check_access, and the optional re-set for timeout refresh, then logs 'Error running get command' and re-raises this wrapper.
Source
Thrown at superset/commands/explore/form_data/get.py:60
def run(self) -> Optional[str]:
try:
key = self._cmd_params.key
state: TemporaryExploreState = cache_manager.explore_form_data_cache.get(
key
)
if state:
check_access(
state["datasource_id"],
state["chart_id"],
DatasourceType(state["datasource_type"]),
)
if self._refresh_timeout:
cache_manager.explore_form_data_cache.set(key, state)
return state["form_data"]
return None
except SQLAlchemyError as ex:
logger.exception("Error running get command")
raise TemporaryCacheGetFailedError() from ex
def validate(self) -> None:
pass
View on GitHub (pinned to f4587218dd)
Solutions
- Inspect the server log for the 'Error running get command' traceback to get the underlying SQLAlchemyError.
- Check metadata DB health and Superset's DB connection pool metrics; restart workers if connections are poisoned.
- Retry the URL after recovery — the cache entry, if intact, will still be there until its timeout lapses.
- Longer term: configure pool_recycle/pool_pre_ping and monitor DB connection counts.
Defensive patterns
Strategy: retry
Try / catch
try:
GetTemporaryExploreStateCommand(...).run()
except TemporaryCacheGetFailedError:
if metadata_db_healthy():
reload_with_retry()
else:
show_maintenance_notice() Prevention
- Keep metadata DB highly available; explore reads depend on it.
- Tune connection pool sizing for peak explore traffic.
- Use 'Error running get command' logs to distinguish DB faults from cache faults.
When it happens
Trigger: Opening an Explore URL with a cached form_data key (GET) while the metadata database errors — unreachable, mid-failover, or with an exhausted connection pool.
Common situations: Dashboard/Explore links failing during DB maintenance windows. Load spikes exhausting the pool so the session/cache-adjacent queries fail. Stale connections after a DB restart behind an unchanged pool config.
Related errors
- An error occurred while creating the value.
- An error occurred while deleting the value.
- You don't have permission to modify the value.
- Invalid connection string, a valid string usually follows: b
- Unsupported cache backend configuration
AI-assisted analysis of apache/superset@f4587218dd (2026-08-14).
Data as JSON: /api/errors/bb232923fe15aadc.
Report an issue: GitHub.