> ## Documentation Index
> Fetch the complete documentation index at: https://docs.talview.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why is the Evaluation form not saving responses?

The evaluation form in **Talview’s Workflow Tools** may fail to save responses for many reasons - from simple client-side problems (browser, connectivity) to server-side issues (validation, permissions, database).

The table below lists common causes and straightforward fixes to help you quickly diagnose and resolve the problem.

***

## 🔎 Troubleshooting Common Issues

| **What might be wrong**                              | **How to fix it**                                                                                                                                    |
| :--------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------- |
| User session expired or user got logged out          | Ask the user to refresh or re-login and retry. <br />Make sure session timeouts are configured appropriately for long evaluations.                   |
| Browser incompatibility or outdated browser          | Confirm the user is on a supported, up-to-date browser (Chrome/Edge/Firefox) and ask them to try again after updating. Test in an alternate browser. |
| Network interruptions or unstable connectivity       | Check network connection: ask user to switch networks or use a wired connection. Implement/retry with exponential backoff for intermittent failures. |
| Form is in read-only/closed state or not published   | Confirm the form is published and editable for the current user and evaluation instance. Re-open or publish the correct version if needed.           |
| Autosave feature disabled or misconfigured           | Check autosave settings; advise user to manually save and submit for now. <br />Re-enable or fix autosave configuration.                             |
| Feature flags or rollout causing unexpected behavior | Check whether any feature flags are active for the org/environment and rollback or enable fixes as necessary.                                        |

<Tip>
  **Additional Tips:**

  * Train evaluators to save frequently and avoid long idle periods.
  * Use supported browsers (Chrome latest recommended) and keep them updated.
  * Avoid using browser back/forward during saves; prefer explicit Save buttons.
  * Keep attachments under platform limits and compress large files.
  * Review release notes before deployments and test evaluation workflows after upgrades.
  * Enable autosave/drafts where available so partial work is preserved.
  * Maintain a checklist for required fields within each evaluation template to reduce validation-related failures.
</Tip>