Persist Cloud tasks
Understand how React reconnects to Cloud jobs after reload and when restored tasks can retry.
React persists resumable Cloud tasks by default. Local tasks remain in browser memory and disappear when the tab reloads.
What is persisted?
Once a Cloud session exists, the React store retains:
- the session ID and client secret;
- task state and output metadata;
- expiry and skipped count; and
- a replayable URL request when one can be serialized safely.
Browser File and Blob data is never written to storage.
The client secret is a session credential
Persistence uses browser storage so the app can resume. Protect the origin from script injection and do not copy stored session data into logs, analytics, or URLs.
What happens after a reload?
- A processing Cloud task reconnects with
resumeZip()and continues polling. - A completed task restores its download metadata while the output is valid.
- Expired output restores as
expiredrather than showing a broken link. - A Local task does not restore.
When is retry unavailable?
Plain URL requests can be retained and replayed. A createSession callback
cannot be serialized, so a restored backend-created task can resume an existing
session but cannot recreate a failed one. Start a fresh download() call in
that case.
Configure persistence
<EazipProvider
config={{
persist: false,
}}
>
<App />
</EazipProvider>Set persist: false to disable reads and writes. Use a custom storageKey when
multiple Eazip-powered roots share one origin.
For manual Core persistence, see Sessions and resume.