What a schedule list can truthfully say about its next occurrence. A floating rule owned by another device has no exact instant here because the schedule schema deliberately stores no owner timezone.
API reference sections
Schema
ScheduleNextFiring
Type object or object
Shape
One of 2 shapes:
kind: "exact"
Field Type Description at_msrequired integer (int64) kindrequired "exact" kind: "owner_local"
Field Type Description kindrequired "owner_local"
{
"at_ms": 0,
"kind": "exact"
}The contract has no example values, so example bodies are generated from each schema: every field is shown with a placeholder of its type.
Generated from contract version 1. Last updated .
