Settings → Organization shows stale/default 90-day retention while Admin shows correct value

[SemoTech]

Summary

After updating an organization's log retention via Admin → Organizations → [org] → Retention Period, the read-only display on Settings → Organization (/dashboard/settings/general) continues to show 90 days, even though Admin correctly shows the updated value (e.g. 365 days).

Hard refresh of the Settings page does not fix it. Admin remains accurate.

Environment

• Self-hosted LogTide (Docker / Portainer)
• Org Settings (member UI): read-only retention card
• Admin Organizations detail: editable retention field

Steps to reproduce

1. As a platform admin, open Admin → Organizations → [organization].
2. Set Retention Period (days) to 365 and save.
3. Confirm Admin still shows 365.
4. Open Settings → Organization (/dashboard/settings/general).
5. Observe Log Retention Policy still shows 90 days.
6. Hard-refresh Settings — value remains 90.

Expected

Settings → Organization should show the same retention as Admin / the database (organizations.retention_days), e.g. 365 days.

Actual

Settings shows 90 days (looks like a default/fallback), while Admin shows the correct 365 days.

Likely cause (from frontend build inspection)

On the Settings general page, retention is rendered from the client org store / cached currentOrganization:

{currentOrg?.retentionDays || 90} days

Admin loads retention via getOrganizationDetails() (fresh API), so it stays correct.

Suspected contributing factors:

1. || 90 fallback — if retentionDays is missing/undefined on the cached org object, the UI always displays 90 even when the server has another value.
2. Stale localStorage org cache (currentOrganization) — Settings appears to read the cached org object and does not re-fetch retention when opening the page after an Admin retention update.

Suggested fix

• Re-fetch organization (or at least retention) when opening Settings → Organization, or update the org store after Admin retention save so all views stay in sync.
• Prefer nullish coalescing with an explicit fetch over retentionDays || 90 so a missing field does not silently look like a policy of 90 days (or show a loading/error state instead).

Impact

Operators believe retention is still 90 days and may “fix” it again or distrust Admin, even though cleanup already uses the Admin/DB value.

[Polliog]

Thanks for the detailed report, the frontend build inspection was spot on. Confirmed on develop, and your two suspected factors are both real:

1. The org store restores the cached currentOrganization object from localStorage on boot, and the dashboard guard only fetches the org list when there is no current org. So once a cached object exists, the list is never re-fetched for that session (only login/register/invite flows refresh it). That is why a hard refresh does not help while Admin (which always fetches fresh) stays correct.
2. The retentionDays || 90 fallback then makes any stale or pre-retention cached object silently render as a 90 day policy.

The backend API already returns retentionDays correctly on every org endpoint, so this is purely a frontend staleness bug.

Fix incoming: the dashboard will revalidate the org list in the background even when a cached org exists (the cache stays, it is only there to avoid a name flash on reload), and the Settings page will no longer coerce a missing value to 90. Will land in the next release.

[Polliog]

Fixed on develop (#293, merge commit e89b6e9). Leaving this open until the next release ships it.

The dashboard now revalidates the organization list in the background whenever a cached organization exists, so a retention change made in Admin reaches Settings without a re-login, and the retention card no longer coerces a missing value to 90 days. Thanks for the precise report, the build inspection saved us the diagnosis.

[SemoTech]

Thanks for confirming and fixing this so quickly (#293). The localStorage + || 90 explanation matches exactly what we saw (Admin correct at 365, Settings stuck on 90 after a hard refresh).

We’ll verify Settings → Organization after the next release lands. Appreciate the precise turnaround.