2026-05-19 - Credential Caching and BigQuery Retry Standardisation¶
Release¶
AgileData.io - Leaner Backend: Fewer External Calls, Faster Processing
Two backend efficiency improvements were deployed this month. They reduce unnecessary calls to external services and make error handling more predictable.
Credential caching — Backend functions now look up their credentials once per request and reuse them. Previously, some requests looked up the same credentials twice. Removing the duplicate call reduces latency and API quota use.
BigQuery retry standardisation — All BigQuery API calls across the backend now use retry=None, meaning failures are reported immediately rather than being silently retried by the default retry policy. This makes errors deterministic and easier to diagnose — instead of a call appearing to hang while retries accumulate, failures surface quickly with clear error messages.
What’s New:
Credentials looked up once per request — no more duplicate calls
All BigQuery calls standardised to retry=None for deterministic error behaviour
Both changes applied consistently across the entire backend
What this means for you:
Faster backend processing with fewer round-trips to external services
Clearer and faster error reporting when BigQuery queries fail
More efficient use of Google Cloud API quotas
Last Refreshed¶
Doc Refreshed: 2026-10-25