Troubleshooting Tenant Settings

The tenant saves, but data stops updating

Check:

• whether the connection still tests successfully
• whether the tenant remains enabled after the change
• whether query or job settings became too restrictive

Messages or alerts look stale after a settings change

Typical causes:

• the next worker cycle has not completed yet
• the hot window or query range no longer covers the expected data
• a source or access setting changed the reachable dataset

Users lost access to the configuration

Check:

• access groups or visibility assignments
• company or scope assumptions after the change
• whether the affected user role still matches the intended audience

Connection tests fail after changing credentials or certificates

Typical causes:

• outdated secret, password, or token
• wrong host, path, or OAuth endpoint
• expired or mismatched certificate material

The change seems correct, but the UI behaves differently than expected

Check:

• whether the setting affects only future sync cycles
• whether another setting in the same area overrides the expected behavior
• whether the impact belongs to worker timing rather than immediate UI logic

When to use the technical docs

Switch to /sysdocs when you need:

• module-level ownership of tenant settings
• exact runtime and worker interactions
• permission and scope internals
• architecture details for sync, jobs, and persistence