Troubleshooting

Connection issues

• Verify URL points to the Zabbix API endpoint.
• Validate API token scope and expiration.
• Confirm TLS certificate chain is valid.
• Confirm the iPhone can reach the target host and network path directly.

Problem actions do not appear

• Confirm you are on a problem row in Active or Recent.
• Refresh the list and retry the swipe or action flow on the selected server.
• If the row state changed after a recent update, reopen the list and confirm the problem is still present in the current mode.

Problem details look incomplete

• Open the problem again after the list refreshes to confirm you are viewing the latest state.
• Check whether the monitored item exposes latest data for the selected problem context.
• Expect relative timestamps and latest-value context only when the upstream data is available for that problem.

Charts do not appear

• Confirm the item is numeric. Chart actions are shown only for supported numeric values.
• Retry from Problem Details or Items after refreshing the current section.
• If the chart opens but looks sparse, compare a short range and a longer range before treating it as missing data.

Items or dashboards look empty

• Confirm the selected server actually exposes hosts, items, or dashboards for the current token scope.
• Re-check the active host selection in Items or the selected dashboard in Dashboards before assuming data is missing.
• For Dashboards, rotate the iPhone to landscape if the reader prompts for it.

Sorting or grouping looks wrong

• Confirm which server is currently selected before comparing list organisation.
• Remember that sorting and grouping are stored as per-server view state.
• Reset the selected organisation controls if the current view reflects an older preference rather than a data problem.

No push notifications

• Confirm iOS notification permission is granted.
• Verify the server edit flow shows push registration as Ready.
• Check that Zabbix webhook uses the latest copied UNIQUE_UID.
• Ask your monitoring administrator to verify push integration settings in Zabbix if delivery is still missing.

Push works in one app version but not another

• Make sure you are using the latest available app build.
• Open the app and wait for server status to refresh to Ready.
• If needed, re-open the server edit flow and confirm push is enabled for that server.

Problem state looks stale after a notification action

• Open the app to let the selected server refresh before comparing the problem state.
• Check the problem in Active and Recent, because the current state may move between views after the action completes.
• If the server still shows the older state, refresh the list and reopen the problem details screen.

Wrong server context

• Re-check which server card owns the current UNIQUE_UID.
• In multi-server setups, confirm the copied UNIQUE_UID was taken from the correct server edit flow.
• If a device was re-registered, update the value in Zabbix user media instead of reusing an older UID.

Safety checks

• Keep your Zabbix API token private and never share it in chat, screenshots, or support tickets.
• Treat push delivery and in-app browsing as separate paths. One can work while the other is misconfigured.