Skip to main content

​
Common Save Error Messages

​
Resolve Transaction Failures

All Risksheet save operations are wrapped in database transactions. If any single item update fails, the entire save operation rolls back to prevent partial data updates.
  1. Note the specific error message displayed in the toast notification
  2. Check if the error relates to a specific work item (look for item IDs in the message)
  3. Verify that you have write permissions on all modified work items
  4. Retry the save. If it continues to fail, undo recent changes to isolate the problematic edit
diagram
Custom Polarion Scripts Can InterfereCustom Polarion workflow scripts that validate work item fields (such as duplicate title checks) can interfere with Risksheet save operations. If saves fail inconsistently across rows, check for custom validation scripts on the affected work item types.

​
Fix “Overwrite Not Supported” Error

This error occurs when the sheet configuration has a conflict between overwrite mode and the refreshOnSave setting.
  1. Open the Risksheet configuration via the configuration editor
  2. Locate the global section and check the refreshOnSave property
  3. Resolve the conflict by either:
    • Setting refreshOnSave to true (recommended), or
    • Disabling overwrite behavior

​
Handle “Discard Changes” Popup After Save

When refreshOnSave is set to false, you may see a browser popup asking “Changes you made may not be saved” when navigating away after saving. This occurs because the UI is not refreshed after save, so the browser still detects a “dirty” state even though changes were saved successfully. Resolution:
  • Upgrade to version 25.8.1 or later where this issue is fixed
  • Alternatively, set refreshOnSave to true to avoid the misleading popup
Your Changes Are SavedIf you see the “Discard changes” popup after pressing Save and you are on a version prior to 25.8.1, your changes were actually saved. The popup is cosmetic. Dismiss it safely.

​
Handle Session Timeout During Save

With concurrent Polarion licenses, your session may expire during long editing sessions. Prior to version 24.8.6, this produced an “unknown communication error” with no clear indication of the cause. Since version 24.8.6, Risksheet shows a proper timeout message with a login link. Quick workaround:
  1. Open a new browser tab and navigate to your Polarion instance
  2. Log in to re-authenticate your session
  3. Return to the Risksheet tab and retry the save
Built-in Session Keep-AliveRisksheet includes a keep-alive mechanism that sends periodic heartbeat requests to prevent session timeout. If you still experience timeouts, check your Polarion server’s session timeout configuration.

​
Resolve Formula-Generated Field Conflicts

Formula-generated fields (such as auto-generated titles) can cause save failures when Polarion permissions restrict editing those fields in certain workflow states. Scenario: A formula generates a title from related fields (e.g., hazardous situation + harm). If the stored title differs from the formula output (for example, after a data migration that truncated titles), Risksheet attempts to save the recalculated value. If permissions block editing the title field in the current workflow state, the save fails. Resolution:
  1. Correct the stored values to match what the formula generates
  2. Or adjust workflow permissions to allow the formula-populated fields to be updated
Items Without TitlesItems with empty or missing titles can cause linking errors. Use formula-based title auto-generation from related fields as a best practice for FMEA workflows.

​
Verify Save Success

After resolving a save failure and retrying:
  1. Save the document and confirm no error messages appear
  2. Refresh the page to verify all changes persisted
  3. Check modified work items in the Polarion work item view
You should now see all changes saved successfully with no error notifications, and the grid reflecting the committed state.

​
See Also