When formula-generated fields don’t match stored values, permission restrictions can block saves even when configuration appears correct.
Check field length limits - If you migrated from an older Polarion version, field length limits may have changed (e.g., title truncated to 80 characters in migration, but current formula generates longer titles)
Compare formula output to stored value:
Open the work item in Polarion’s native editor
Note the current field value
Check your formula configuration to see what value it generates
If values differ, manually update the field to match the formula output
Review permission rules - Check that status transition rules allow modification of all fields affected by your formulas
When formulas generate field values that don’t match stored data (common after Polarion version migrations with changed field length limits), permission restrictions evaluate the mismatch and block saves even when permissions are configured correctly. Manually correct stored values to match formula outputs.
Versions prior to 25.8.1 trigger spurious “discard changes” pop-ups when refreshOnSave is set to false.Check your version:
RISKSHEET 25.8.1+ (released August 21, 2024): Issue resolved (NPT-1060)
RISKSHEET pre-25.8.1: Upgrade to eliminate spurious pop-ups
Configuration in risksheet.json:
Copy
Ask AI
{ "global": { "refreshOnSave": false }}
Expected behavior by version:
Version
refreshOnSave: false
refreshOnSave: true
< 25.8.1
Spurious pop-up after save
Normal save, auto-refresh
≥ 25.8.1
Clean save, no pop-up
Normal save, auto-refresh
Setting refreshOnSave: false prevents the page from reloading after save, which preserves cell selection and scroll position. Version 25.5+ also includes a fix (“Preserve cell selection and scroll position after save”) that works with refreshOnSave: true.
If saves fail occasionally (e.g., 1 out of 15 operations), investigate network stability and session state.
Check browser console - Press F12 and look for JavaScript errors or network failures during save
Review Polarion server logs - Look for exceptions or timeout errors coinciding with failed save attempts
Test with different browsers - Browser-specific issues can cause intermittent failures (see Browser-Specific Issues)
Monitor session timeout - If your license has limited timeout settings, saves may fail when session expires (see Session Timeout Errors)
Reduce batch size - If editing many cells before saving, try saving more frequently to reduce transaction size
Support tickets indicate intermittent save failures (occurring once per ~15 saves) are difficult to diagnose without detailed log analysis. Enable detailed logging in Polarion and capture the exact error message and timestamp for support investigation.
