Skip to main content
August 29, 2026 Documentation correction Action required

​
Affects

Teams that test Reporter Data Source connections or retrieve their schemas.

​
What changed

The documentation now correctly states that the connection probe identifies a Data Source with dataSourceId. A probe returns connected or failed, together with message and latencyMs. Schema discovery is a separate operation, not a probe result. This is a documentation correction of the current runtime behavior; it does not announce a runtime release.

​
Impact

Classification: Action required.

​
What you need to do

Use dataSourceId in probe clients. Treat a successful probe as connection validation only, then call the schema operation before relying on tables or fields.

​
Deadline

Update affected clients and runbooks before the next Reporter deployment.