This article describes how tasks restart after platform downtime.
Auto-resume from checkpoint
The tasks in this section automatically continue from where they left off. No action is needed after downtime.
| Task |
| Native upload: Processing stage (post transfer) |
| Native upload through through Purview, Google Vault, or Slack cloud connection |
| Native upload through Cloud Storage: Box, Google Drive, OneDrive, Dropbox, SharePoint, ShareFile, iManage cloud, Direct Link |
| Processed upload: Processing stage (post transfer) |
| Apply or delete batch redaction |
| Batch delete documents from the results table |
| ZIP export from the results table |
| Project export from Database Settings or Organization home |
| Production creation |
| Reindexing: Attachment grouping, versions, exact duplicate, chat-conversation, and email threading |
| Predictive coding model update |
| Batch Review Assistant AI action |
| Storybuilder batch summary generation |
| Deep Dive enrollment |
| Reprocessing |
Manually resume from checkpoint
The tasks in this section maintain their progress, but must be manually resumed by a user; these tasks do not restart on their own. When downtime is over, follow the instructions in the To restart column to restart the task.
| Task | To restart: |
| Native upload from a local source (your computer, not a cloud connection): Transferring step | When prompted, select Retry on the interrupted source in the native upload’s file list, then reselect the original local file or folder. |
| Processed upload: Transfer and configuration (before upload completes) | On the In progress tab: Select Configure upload on the relevant upload card. This takes you to the step you were on previously. local file sources may need manual reselection. |
Auto-restart from beginning
The tasks in this section automatically restart, but back from the beginning. No action is required, but previous progress is lost.
| Task |
| Batch add/remove documents from projects |
| Batch modify work product (Apply or remove codes, binders, or ratings; add to Storybuilder) |
| Batch assign documents |
| Production packaging/repackaging (post creation or modification) |
| CSV, PDF, or LFP export from the results table |
Manual restart
The tasks in this section must be manually restarted, back from the beginning. When downtime is over, follow the instructions in the To restart column to restart the task. Partial effects may remain.
| Task | To restart: |
| Downloading a completed production | Restart the download from its card on the Productions page |
| Download a completed export | Restart the download from the relevant card in the Batches & Exports column of the homepage |
| Create an assignment group |
Restart creating the assignment group. If an assignment group was in the initializing phase when downtime started, you may need to reach out to support@everlaw.com to clear it out. |
|
Note Some documents may have run through the task, but you need to restart the task from the beginning to complete the remaining documents. |
Restart from Project Settings > Categories and codes > Import/apply review work |
|
Persistent highlight import: Via CSV or from a Search Term Report Note Some highlights may have run through the task, but you need to restart the task from the beginning to complete the import. |
Restart from Project Settings > General > Persistent hits > Import list |
|
Native upload through through Zoom, Jira, Asana, Zendesk, or Salesforce cloud connection Note Some documents may have run through the upload, but you need to restart the task from the beginning to upload the remaining documents. |
Restart from the Native upload page |