Billing and connector reliability improvements across tenant access, scheduled sync, and API key management

Context #

The benchmark-category changes for 2026-04-06 are centered on a billing and connectors area that received a concentrated set of fixes and feature work. The Git evidence shows multiple updates focused on tenant resolution, scheduled synchronization, connector authorization, API key handling, error handling, and dashboard-facing billing views.

What changed #

A clear theme in the changes is operational reliability for billing workflows:

Tenant resolution logic was revised several times, especially around demo-tenant access and role assignment.
Scheduled and internal billing sync flows were tightened, including cron-triggered paths and daily reporting.
Cost synchronization behavior was updated, including support for automatic month selection.
Connector authorization was standardized behind a dedicated authorization endpoint.
API key handling for connectors gained encrypted storage support, along with UI and endpoint changes.
Billing dashboard and related enterprise views were updated in parallel, suggesting the backend changes were reflected in user-facing management screens.

Why it matters #

These updates reduce failure modes in a part of the product that depends on correct tenant context, secure credentials, and dependable background execution.

The most important practical outcomes are:

Fewer authorization mismatches for demo and internal service-account scenarios.
More predictable scheduled execution for billing aggregation and reporting.
Improved security posture for connector credentials through encrypted API key storage.
Lower integration friction by unifying connector OAuth URL handling.
Better resilience in billing APIs through broader error-handling improvements.

User-facing impact #

For users and operators, the likely effect is a more stable billing experience:

Demo access should behave more consistently in tenant lists and role-dependent flows.
Connector setup should be easier to complete because authorization routing is more consistent.
Connector credential management should be safer and more production-ready.
Billing dashboards and KPI-related screens should better align with the latest backend logic.
Scheduled billing jobs and recurring reports should be less likely to fail due to authorization edge cases.

Benchmark-oriented interpretation #

From a benchmark perspective, this change set improves the system's readiness for reliability and regression evaluation rather than introducing a new public benchmark suite.

The evidence supports tracking at least these benchmark dimensions:

Tenant-resolution correctness under demo, admin-level, and cron-driven contexts.
Sync job success rate for scheduled billing operations.
Error-handling quality for cost synchronization and connector APIs.
Connector onboarding completion rate after authorization flow unification.
Secret-handling compliance for stored provider API keys.

This is also a good candidate for targeted ablation-style validation: isolate tenant resolution, cron authorization, and connector credential handling independently so regressions can be attributed to one control surface at a time.

Implementation notes #

The code footprint spans billing libraries, API endpoints, enterprise UI components, connector authorization logic, tests, and help metadata. That spread indicates coordinated changes across both service logic and operational surfaces, not a documentation-only refresh.

There is also a current working-tree modification in a CI auth-token JSON file and an untracked credentials JSON file in the repository state. Those do not appear to be part of the committed product change set and should not be treated as shipped functionality.

Outcome #

Overall, the date's benchmark-category work is best understood as a reliability and security hardening pass for billing-platform operations, with added support for encrypted connector API keys and a cleaner authorization path for connectors. The result should be stronger day-to-day execution for tenant-aware billing workflows, especially in scheduled and integration-heavy scenarios.