Recovered sessions
sessionRecovery in your CSVImporter options persists unfinished imports for a later visit. By default ExpressCSV stores no importer state.
Recovery Fingerprint
Recovered sessions are stored against a combined fingerprint of two values:
-
importNamespace, the stable namespace string your app assigns to this importer configuration -
the schema shape
-
ExpressCSV first uses
importNamespaceto decide whether a saved browser session belongs to this importer, then falls back to schema fingerprints when needed. -
Keep
importNamespacestable for the same workflow (for exampleproduct-import); use a different value for a genuinely different importer. -
If
importNamespaceor the schema shape changes in an incompatible way, ExpressCSV may start a new session instead of recovering the old one.
Local Recovery
Use the built-in browser persistence backend:
This uses ExpressCSV's default browser persistence implementation and requires no extra code from your app.
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:
RecoveredSessionData
RecoveredSession
Recovery Key
SessionRecoveryKey is an opaque string generated by the SDK. Treat it as a lookup key only.