Recovered sessions
Pass the sessionRecovery option to useExpressCSV() when you want the importer to restore unfinished imports on the next visit.
By default, ExpressCSV does not persist importer state. If you omit sessionRecovery, unfinished imports are not stored and no Recovered sessions will be available later.
Recovery Fingerprint
Recovered sessions are stored against a combined fingerprint of two values:
importIdentifier, which should represent the same import flow over time- the schema shape
To keep recovery working across visits, treat both values as stable for a given flow. If either changes in an incompatible way, ExpressCSV may treat it as a different import flow and start a new session instead of recovering the old one.
Local Recovery
Use the built-in browser persistence backend:
Custom Recovery
Use type: "custom" when you want to persist recovery data in your own backend.
Adapter Contract
Your custom adapter only needs three methods:
Recovered Payload
Recovered Session
Recovery Key
SessionRecoveryKey is an opaque string generated by the SDK. Treat it as a lookup key only.