flexmeasures.api.v3_0.utils

Functions

flexmeasures.api.v3_0.utils.use_legacy_job_responses(asset: GenericAsset) → bool

Whether API v3 job endpoints should use legacy response behaviour.

Production deployments configure maximum incompatible client versions keyed by asset attributes, which are looked up on the asset and its nearby parent hierarchy.

Legacy behaviour means synchronous sensor-data ingestion, HTTP 200 from accepted scheduling and forecasting triggers, and HTTP 400 while polling an unfinished schedule.

For QA, an assumed-version mapping can supply a version when the relevant asset hierarchy does not define that attribute itself.