When something goes wrong
StoryVault presents feedback as messages, dialogs or status information on the affected job. Note the exact wording and the step involved. A missing success message alone does not prove that an action did not run.
Understand the error
Section titled “Understand the error”Short messages often appear at the bottom right and disappear after a few seconds. Some offer a retry. Check the existing job first to avoid starting an upload or AI request twice.
| Message | What to check | Next step |
|---|---|---|
| Connection failed | Is the internet working? Is an upload or recording still running? | Keep originals, reconnect and check status before retrying. |
| Not authorized | Correct tenant, module, role/capability and access to the specific object? | Ask your administrator; a higher role alone does not resolve every access restriction. |
| Session expired / not signed in | Is the login still valid? | Save open edits and local recordings before signing in again. Unsaved input is not automatically protected. |
| Too many requests / rate limit | Does the message specify a wait time? | Wait as instructed and reduce parallel requests. Repeated clicking may extend the problem. |
| Server error / 500 | One step or the whole application? | Note the time and error text; contact support if it persists. An error report does not guarantee a response or that someone is already working on it. |
Distinguish upload and processing errors
Section titled “Distinguish upload and processing errors”A connection interruption may stop an upload, or only its final confirmation may be missing after the data was transferred. Look for the session in the correct tenant and project and check its status before uploading again.
A status such as Processing or Transcription refers to another work step. Uploading again does not automatically fix that step. Keep local originals until transfer is confirmed and you have checked the recording in StoryVault. See Upload and iPhone app.
Deletion and recovery
Section titled “Deletion and recovery”Read confirmation dialogs carefully. Not every action or data type can be recovered. The Trash can help with supported objects; it does not guarantee recovery of permanently deleted files or permanently anonymized data. Check the specific function and retention rule before deleting.
Attachments with many pages
Section titled “Attachments with many pages”Text extraction is limited to 200,000 characters per attachment, roughly 50,000 tokens. This is not a fixed number of pages or words. The model context window further limits what fits into a particular request. Observe any warnings: a fully stored file does not prove the AI considered every page.
Work through the problem
Section titled “Work through the problem”- Note the error and affected step; preserve local originals first if a recording is active.
- Check connectivity and the existing job status. Use an offered retry deliberately.
- For display problems, save open edits before reloading. Do not routinely clear browser data.
- If the problem persists, provide the time, device, app/browser version and checks already performed to your administrator or support. Crop screenshots and redact confidential information first.
Reinstallation, clearing browser data or flashing firmware is not a standard fix for an unprotected recording.