startAt

Start the scroll at this point id, inclusive, so a job that was interrupted resumes where it stopped instead of re-reading from the beginning. null (default) starts at the first point.

Inclusive is Qdrant's own cursor semantics, not a choice made here: resuming from the last id a previous run handled reads that one point again. For an idempotent consumer — anything keyed by point id — that is a repeat rather than a duplicate.

An id-ordered scroll reads in ascending id order, which is what makes an id a valid cursor at all. Ignored by an ordered scroll, which resumes through orderBy's startFrom because Qdrant returns no id cursor for one.