basalt / drives/src / DriveCursorResetError
Class: DriveCursorResetError
Defined in: drives/src/errors.ts:223
The stored change cursor is no longer usable and the feed must be restarted.
Every one of the three vendors can say this, and phase 1 had no way to express it: Dropbox answers 409 reset/ when a list_folder cursor has aged out, Microsoft Graph answers 410 resyncRequired, and Google Drive invalidates a pageToken the same way. Mapped to any other error, a sync fails on every run for ever — the cursor that caused it is persisted, so nothing ever clears it and no amount of retrying helps.
The engine answers by dropping the cursor and stopping the run; the next run re-primes the feed from the start and the import ledger absorbs the repetition, so a reset costs metadata reads rather than a re-download.
Extends
Constructors
Constructor
> new DriveCursorResetError(provider, detail?): DriveCursorResetError
Defined in: drives/src/errors.ts:225
Parameters
provider
string
detail?
string = 'the change cursor is no longer valid'
Returns
DriveCursorResetError
Overrides
Properties
code
> readonly code: string
Defined in: core/src/errors.ts:25
Inherited from
details?
> readonly optional details?: Record<string, unknown>
Defined in: core/src/errors.ts:28
Structured payload passed to the constructor, exactly as given (never sanitised here).
Inherited from
status
> readonly status: 409 = 409
Defined in: drives/src/errors.ts:224