Recover an upload and open a document¶

Use the document action on the record, request, correspondence or Shared work item you are working with. Keep that source context while recovering: the same file name in another upload or workspace is not the same attempt.

Experience described: the steps below follow the WorkOS final designs for upload recovery and the read-only viewer. The frontend is still being connected and includes sample screens. This guide describes the intended experience with the current service rules; it does not confirm that every control is available in your deployed workspace.

The ordinary recovery steps are for signed-in work. Public Records submission uses a separate journey, described below and in the public intake guide.

Before you begin¶

• Use the same account and workspace that started the upload, and keep the original file available.
• Check the destination action and its allowed file type. Do not change the file while continuing the same upload.
• Keep enough workspace storage available. If the application cannot check the allowance, wait for the issue to be resolved instead of creating repeated uploads.
• Use the source action's result to confirm attachment or submission. Upload progress alone does not confirm either.

Files for a public Records submission¶

Begin from the intake address supplied by the receiving organization. Follow its submission guide for the form, main document, supporting files and receipt. The upload belongs to that submission context; signing in later does not transfer it into ordinary account upload recovery. Starting through public intake while already signed in also does not establish that this separate recovery page can retrieve the attempt.

Check the active intake page's per-file size and allowed formats before choosing files. The current defaults allow PDF, JPEG, PNG and Word documents up to 25 MiB each, with one main document and at most nine supporting files. Use the active intake page's limits when they differ from these defaults. An allowed filename or stated file type does not establish that the file is safe or that its contents have been verified.

Keep the original files until the submission is confirmed. Finishing their upload only prepares them for the final submission; it does not create an official record number or prove acceptance by the registry. Keep the receipt separately from temporary upload information. A receipt is for the submission, not a way to resume an unfinished transfer or open every internal record detail.

If the intake page asks you to wait after too many attempts, allow time before trying again. For an interrupted or uncertain result, stay with the original intake journey and use the receiving organization's support route. Do not start duplicate submissions solely because an upload response or status check is missing. Connected public recovery and receipt-status access remain under verification, so the designed no-sign-in journey is not yet a hosted availability guarantee.

Continue an interrupted upload¶

1. Return to the source document flow. In the inspected Records design, recovery appears over the selected record's Documents page.
2. Check the file name, uploaded amount and Available until time in Continue uploading this file. Confirm this is the attempt you want to continue.
3. Choose Continue upload. The application should use the service's current saved progress. It must not replace already accepted parts with different bytes.
4. Keep the original file available if the browser needs it. If the original has changed or is unavailable, stop and use the source flow's supported new-upload path.
5. When the transfer is complete, continue with Finish upload below.

There is no guaranteed browser-local retention period in the shared service. A displayed progress percentage is not proof that every file part has been checked or that the destination item has changed. If an earlier response was lost, recover current progress before starting a duplicate attempt.

Finish the upload and use the file¶

1. In Finish uploading this file, confirm the file and that all parts have been uploaded.
2. Choose Finish upload. The service assembles the parts, checks the expected bytes and checksum, applies the ordinary type checks, and prepares the staged file.
3. If the file is Ready for use, choose Done to return to the source flow.
4. Complete any source-specific attach, save or send action. Check the resulting item and selected file/version before treating the work as finished.

“Ready for use” describes a prepared file. It does not by itself mean that a record was filed, a memo sent, a request approved or a recipient notified. If finishing fails or its response is uncertain, check the source and current upload state before retrying. Do not choose a new attempt simply to clear an uncertain result.

Discard an upload you no longer need¶

1. Check that the temporary upload is the one you intend to abandon.
2. Choose Discard upload.
3. In Discard this upload?, choose Keep upload to return, or Discard upload to confirm abandonment.
4. Return with Back to documents when the result allows it. If removal is still pending, treat the upload as unavailable for use and let support investigate cleanup when necessary.

Discarding the temporary upload does not delete an existing source document or undo a completed business action. A file already reserved or consumed by a source operation cannot be discarded through this ordinary action. Physical removal can be queued after a storage failure, so the confirmation must not be treated as immediate erasure evidence. Do not use an old temporary link to try to recover an abandoned file.

When an upload expires¶

The Upload expired design offers Choose file again and Back to documents. First confirm whether the source action already succeeded. If a fresh upload is needed, choose the current original file from the source flow and start a new session. An expired session cannot simply be extended by refreshing its recovery page.

The application should suppress resume, finish and discard controls when the recovery response says the upload has expired, even if background cleanup has not run yet. A remaining temporary row or old progress indicator does not make the upload usable.

Open and use the read-only viewer¶

1. From the authorized source page, choose the intended document and saved version, then its Open or View file action. Use that source guide for the exact entry point.
2. Confirm the file title in the viewer. The inspected design shows Read only, the time access ends, a page list and page/zoom controls.
3. Move through the document using the controls provided. Reading does not modify its content or complete an approval.
4. Use Download only when offered for that source and permitted for your task. A downloaded copy is a separate local copy; handle it under your organization's rules.
5. Choose Close when finished to return to the source context.

The current frontend is a sample preview: you can move between three sample pages, but Download does not retrieve a file. Its file title and access times are examples; expiry is not checked against a real viewing session. Use a connected, authorized source flow before relying on a file or an access deadline.

Recover when viewing fails¶

If This viewing session has ended appears, choose Close viewer, return to the source page and open the file again. Reopening lets the source flow select the right file and create fresh access; copying an old link or another person's session does not restore access.

A file link can expire before its viewing session. For an unavailable or blank document, verify the selected source/version and current access, then follow the source guide's retry path. If the result is uncertain or failure repeats, contact support with the workspace, source reference, file name, approximate time and visible error. Do not include temporary links, session tokens or confidential file contents in an ordinary support message.

Use Shared work viewing, Records or correspondence for source-specific permissions and recovery. Use document history to interpret recorded access; an entry does not prove that a browser received or read the file.

See document reliability and help for the meaning of operation counts, the last confirmed result and useful support information.