Troubleshooting

Troubleshoot missing emails, rows, and automation runs

Find the submission in Received before changing an automation. Confirm its delivery and processing status, then check the destination that is missing an output. A submission detail panel with processing and file information. Missing output Check first File in cloud storage The file’s destination, connection health, folder permissions, and delivery status. Team email Selected recipients, saved page configuration, spam folder, and the completed submission. Uploader confirmations and custom email templates are not wired to current delivery. Google Sheets row Sheet connection, selected file and tab, row mode, authorization, and whether the submission qualifies for any backfill you requested. Zapier or Make run The workflow is enabled in that service, connected to the intended workspace and upload page, and maps the current fields. Webhook request The endpoint is attached to the page, reachable, and returns a success response. Check signature verification and receiving-server logs. AI values Extraction columns are saved, the file is supported, credits are available, and the processing outcome permits a result. Avoid duplicate work A file can finish uploading before a later step fails. Check each system before repeating a submission, reconnecting a Sheet, or replaying a workflow. Use the submission ID as a stable reference; design receiving automations to handle repeated delivery without creating another record. A webhook or integration payload contains submission data and file references. It does not grant the receiving service your storage permissions or include the file bytes. Check the receiving account’s access if a link cannot open. After changing fields Review mappings after renaming, removing, or recreating a question or AI column. A replacement field can have a different identity even if its label matches. Test a new sample submission and confirm the intended row, record, or task. Read the setup guide for Sheets, Zapier, Make, webhooks, or AI processing. Send support the submission ID, time, and failing stage if the outcome remains unclear.

Troubleshooting

Find the symptom below. If you are collecting files, inspect the matching submission before asking someone to upload again. Submission details used to check file and processing status. Symptom Start here Sign-in email missing or link expired Sign-in and recovery . Request a fresh link and check the email address. Workspace or page missing Workspace selection and page library . Check membership and archived pages. Uploader asked to sign in Copy the public link from Share, not the editor URL. Sharing guide . Page disabled, expired, archived, or blocked by plan Page availability . Check the notice before re-enabling. Page will not enable or save Check highlighted field labels, choices, passwords, destinations, and plan requirements. Create a page . File rejected, upload interrupted, or outcome uncertain Fix upload problems . Check for a completed file before retrying. Storage connection needs attention Destination health . Reauthorize the correct owner or choose an accessible folder. File in the wrong folder or with an unexpected name Folder organization . Compare saved rules and submitted answers. Questions appear or become required at the wrong time Conditional fields . Check the earlier source question and all/any rules. Missing email, Sheet row, webhook, or external run Troubleshoot automations . Find the failed stage. AI missing, skipped, or inaccurate AI processing and credits . Check file support, balance, outcome, and extraction hints. Embed clipped or blank Embed guide . Check the hosted page, website block, height, and allowed origin. Payment or seat change uncertain Plans and billing . Read the current status before repeating checkout. Get help with an unresolved problem Contact support with the workspace, page or submission ID, storage provider, exact error message, and approximate time. Mention the checks you completed. Send a cropped screenshot with private details removed if it helps. For suspected unauthorized access, billing disputes, or a deletion request, contact support directly. Do not send passwords, API tokens, private documents, or payment card details.