Onboarding loops
If the app returns to onboarding after you save the region or organization profile, confirm that the profile fields are complete and that the save action reports success. A stale browser session can also show old state; log out and back in if the profile was just changed.
Missing buttons or sections
Missing buttons usually indicate role or policy restrictions. Review the member role, organization policy thresholds, billing state, and subscription status. For review actions, the user needs review access. For partner actions, the user must meet the trusted-partner policy threshold.
Blocked reports or incident access
Reporting and incident access can be unavailable if the organization subscription is not active. Check billing first, then confirm the user's role. If the submit button shows an error, read the toast message and fix the missing or invalid field before retrying.
Map placement issues
The incident map uses saved organization site coordinates. If incidents do not appear where expected, confirm the report used a mapped site and that the site latitude and longitude are correct. Reports without saved site coordinates may still exist but cannot be plotted accurately.
Partner workflow blockers
If a relationship cannot be accepted, check the connection state, signer metadata, MOU status, NDA status, and whether the receiving organization is the one attempting to accept. Requested relationships are not the same as connected relationships.
Notification issues
- Confirm the event is enabled in personal alert preferences.
- Check the minimum severity threshold.
- Verify quiet hours do not suppress the expected notification.
- For SMS, confirm a destination number exists.
- Confirm organization notification defaults are configured for the event.