This article explains common issues related to AI Form Fill and AI Template generation using Storm across Dashpivot and Sitemate Mobile. It covers missing AI features, processing delays, incomplete field population, upload failures, template formatting inconsistencies, transcription issues, offline limitations, and language-related output discrepancies.
If you are experiencing processing delays, missing buttons, formatting issues, or transcription anomalies while using Storm AI features, select your specific issue below to view the fix:
Missing Features or Disabled Buttons
AI Form Fill is taking too long to process
Storm left fields blank or mapped photos incorrectly
Voice recordings are transcribing or matching incorrectly
Supplier or person name came out wrong
AI Form Fill is not working offline
AI Template generation failed or files are unsupported
Imported templates look incorrect or are missing logic
AI summaries or multi-language outputs look incomplete
Missing Features or Disabled Buttons
What is happening: AI Form Fill is not appearing inside your active form, or the Fill button remains greyed out and unclickable.
Why this happens: The feature might be deactivated at the workspace or template level by an administrator, or the AI canvas is currently empty and lacks the initial data required to begin processing.
How to fix it:
Verify System Access: Contact your Org Controller or system administrator to confirm that AI Form Fill is enabled for your workspace and that the specific template supports AI automation. Try refreshing the form after changes are made.
Unlock the Fill Button: Add at least one supported input type to the canvas area. The button activates immediately once you record audio, type notes/instructions, or upload a .jpg/.png photo.
Still need help? If the feature remains missing after verification, contact Sitemate Support with your template name and screenshots.
AI Form Fill is taking too long to process
What is happening: The processing wheel keeps spinning, or the draft data takes several minutes to populate your form fields.
Why this happens: Processing time scales directly based on audio recording length, the number of uploaded photos, underlying form complexity, and local internet connection quality.
How to fix it:
Use Web Background Processing: On Dashpivot Web, select Come back later. Storm will safely finish drafting your data in the background while you continue working elsewhere. Note that forms with large multi-row tables can take up to 6 minutes — this is expected, not a failure.
Optimize Your Data: Wait for the active processing to complete. For future submissions, reduce the number of uploaded files or split large recordings into smaller sessions.
Still need help? If processing routinely fails or times out, please check your network connection speed or contact Sitemate Support.
Storm left fields blank or mapped photos incorrectly
What is happening: Specific form fields remain blank after processing finishes, or uploaded photos are attached to incorrect sections or table rows.
Why this happens: Storm operates on a strict confidence rule. If the system cannot confidently determine spoken information, dropdown items, or image placements, it intentionally leaves fields blank for manual review instead of guessing.
How to fix it:
Manual Adjustment: Review the document and complete blank fields manually. You can drag and drop photos to adjust their placement if needed.
Improve Input Structure: For future runs, upload photos in a logical chronological order, separate unrelated photos into different sessions, and provide more descriptive voice recordings with clearer context. Frame photos deliberately — a close-up of a defect reads as defect evidence, a wide shot reads as site context. For OCR-critical photos such as dockets and nameplates, shoot flat and square-on in good light.
Still need help? All AI-generated fields behave like standard form text and remain fully editable. If massive chunks of data are routinely dropped, contact Sitemate Support.
Voice recordings are transcribing or matching incorrectly
What is happening: Spoken words are transcribed inaccurately, or Storm fails to recognize and select options from your dropdown menus and linked lists.
Why this happens: Accuracy is driven by audio clarity. High background noise, multiple people speaking over each other, unclear speech, microphone hardware issues, or using abbreviations/shorthand language will degrade matching performance.
How to fix it:
Speak for the System: Use clear, specific terminology. Reference full names and exact configured text options where possible, and avoid shorthand slang. Avoid dictating asset IDs, serial numbers, or docket numbers without a backing photo. Storm won't fabricate a number it can't read — photograph the nameplate or docket instead.
Control Your Audio Environment: Speak clearly and naturally, reduce background environmental noise, avoid overlapping chatter, and use shorter recordings where practical. Verify your dropdown configurations if errors persist.
Still need help? If exact terms are consistently ignored by Storm, contact your system administrator to ensure your form's dropdown lists are up to date.
Supplier or person name came out wrong
What is happening: A company name, person name, or asset name is spelled incorrectly in the generated output.
Why this happens: Storm relies on audio for names when no photo is provided. Audio transcription of proper nouns can be inaccurate, especially for unusual spellings.
How to fix it: Photograph the docket or nameplate — OCR overrides audio for spellings. If the name appears in a linked-list dropdown preloaded with the correct spelling, Storm will fuzzy-match the spoken name to the correct entry automatically.
AI Form Fill is not working offline
What is happening: You cannot initiate processing or view AI-drafted responses while working without a network connection.
Why this happens: Dashpivot Web requires active internet access to reach Storm cloud servers. Dashpivot Mobile supports offline caching but cannot run the active AI processing phase until a connection is established.
How to fix it:
On Dashpivot Web: Connect your device to the internet before attempting to use AI Form Fill features. Offline processing is unsupported on browsers.
On Dashpivot Mobile: Continue recording voice notes, uploading photos, and typing notes while completely offline. Your inputs are saved locally; processing will begin automatically the moment internet connectivity is restored.
Still need help? If your mobile app fails to process queued inputs after returning to cell coverage, try toggling your network connection or restarting the app.
AI Template generation failed or files are unsupported
What is happening: You encounter a failure error or an unsupported file message when uploading a document to generate an automated template.
Why this happens: The source file is corrupted, password-protected, encrypted, saved in an unmapped extension, or exceeds maximum upload limits.
How to fix it:
Clean Your Source File: Re-export the document from its native design application to clear internal errors, and remove any password protection before uploading.
Observe System Limits: Ensure your file format is supported (.pdf, .docx, .xlsx, .csv, .png, or .jpeg) and reduce the overall file size if needed.
Still need help? If clean, unencrypted documents continue to fail, contact Sitemate Support with the exact file type and size details.
Imported templates look incorrect or are missing logic
What is happening: Your generated template structure looks warped, text headings are misaligned, or original conditional logic and math formulas are missing.
Why this happens: Complex structural layouts, multi-column configurations, or low-quality document scans can distort interpretation. Advanced dynamic system features like conditional visibility logic and formulas are not supported during the initial AI structural build.
How to fix it:
Refine via the Editor: Open the standard Dashpivot template editor to manually refine layout structures, fix fields, and configure your mathematical formulas or visibility logic blocks directly.
Improve Scan Clarity: For future setups, upload cleaner digital source files and avoid heavily scanned, crooked, or unreadable paper documents.
Still need help? AI Template generation is built to handle the heavy lifting of initial field creation. Fine-tuning complex layouts should always be handled via the standard template editor before publishing.
AI summaries or multi-language outputs look incomplete
What is happening: The generated draft looks truncated, skips over key field context, or fails to interpret translated outputs accurately.
Why this happens: Mixed-language voice recordings, shifting languages rapidly mid-sentence, unclear pronunciation, or template language mismatches can confuse the context processing engine.
How to fix it:
Review and Supplement: Manually review and correct your text drafts before saving or submitting the form. Users remain strictly responsible for verifying all operational text.
Stabilize Future Inputs: Provide clearer context descriptions, use supporting photos, break large complex workflows into smaller sessions, speak clearly, and avoid shifting languages within a single recording. To keep output in the original spoken language, state this explicitly in your recording — for example, 'write this in Spanish' or 'don't translate.'
Still need help? Storm generally attempts to generate responses in the specific language used by the destination template. If text remains consistently flawed, verify your master template language profile.