Automatic Data Retry
You do not have to chase your grid operator for missing days or unreliable values. Once a meter is connected, energiedaten.at re-requests them, and you can follow each request in the data calendar.
What gets re-requested
Missing days. A day counts as missing when the meter has no reading at all for it. A daily check finds these days and asks the grid operator to send them again. This runs on every plan.
Unreliable values. A day that contains readings of quality level L3 is requested again as well. L3 values are estimates that are not suitable for billing, and the grid operator has to replace them with reliable values (L1 or L2) within 60 days. Our request asks for the better values sooner. This applies to electricity meters from the Plus plan upwards.
The requests have limits:
- Only days after your consent began are covered. For earlier periods, use a historical data request.
- The most recent days are left out, because yesterday's and the day before's data may not have arrived yet.
- A meter that was connected only recently is not checked right away.
- Days outside your plan's data retention are not requested.
- Integration test meters are not included.
- Days that a meter without interval data shows as projected are not requested again, because no measured values will ever follow for them.
How the plan changes it
Higher plans start the checks earlier after a gap appears and repeat the request more often, so gaps close faster. On Pro, BYO Pro and Enterprise, unreliable values are requested particularly early and several times. The pricing page lists what each plan includes.
The plan only sets how soon and how often we ask. The grid operator decides when replacement data arrives, and it can reject a request.
What you see
You do not have to switch anything on. To follow a request, open the meter, go to the Data Coverage tab and select a day in the calendar. Under Resend history you see each request with its date, whether it was automatic, the attempt number and its state: requested, in delivery, delivered or rejected. For unreliable values, the entry also shows how many unreliable readings the day had before the request and how many it has now.
Difference from a historical data request
| Automatic data retry | Historical data request | |
|---|---|---|
| Triggered by | A daily check | You, once, when connecting or later |
| Covers | Gaps since your consent began | The period before your consent began |
| Repeats | Yes, on the schedule of your plan | No, one request per period |
| Depth | Limited by your plan's data retention | Up to the historical depth of your plan |
If you want older data, request it once as described in Requesting Historical Data.
