Submission scheduling
Read the current definition before each scheduled submission. Its submissionRules tell you whether to submit complete delivery days before a gate or a continuous rolling forecast.
| Rule | Gate closure | Rolling |
|---|---|---|
| Coverage | Every interval of each submitted local day | At least 48 continuous hours; partial boundary days allowed |
| Start | A day within the configured delivery horizon | The current grid interval, with the tolerance below |
| Deadline | Market gate minus submissionLeadMinutes | No gate deadline |
Gate-closure submissions
Calculate the market gate from the delivery day, gateDaysBeforeDelivery, gateLocalTime and the definition's time zone. Subtract submissionLeadMinutes. The request must arrive before that deadline.
For example, a gate at 10:00 on D-1 with a five-minute submission lead means arrival before 09:55 local on D-1. Read the actual values from the definition.
Every submitted day must contain all its required intervals. Local days can be shorter or longer at a daylight-saving change; use the rules in Time zones and delivery days.
Rolling submissions
Submit at least 48 consecutive hours whenever a new forecast is ready. The first timestamp must be no more than one hour before server receipt and no later than the first grid timestamp at or after receipt. Starting at the current grid interval provides some tolerance for transmission time.
The 48-hour minimum is measured from the first submitted interval. You can extend the forecast through the final allowed local delivery day. Split values into local-day containers; complete boundary days are not required. Rolling responses do not include deadlineAt.
Delivery horizon and ordering
horizon.firstDeliveryDayOffset and horizon.maxHorizonDays identify the first and last delivery-day offsets from today in the definition's time zone. Refresh these values and submission rules instead of hard-coding dates.
Sort delivery windows by deliveryDay and values by validTime, with each required series and output present. See First submission for a complete payload and Validation & retries for handling failures.