Troubleshoot visible Anywe states
When an action does not finish as expected, use the state shown in the app before trying another action. Anywe surfaces loading text, pending controls, alerts, and empty states in the screen that owns the action.
Retry after an observable failure
| What you see | What to do |
|---|---|
| Button is pending or disabled | Wait for the request to settle; do not repeat the action |
| Alert, toast, or inline error | Check the connection and retry from the same screen |
| Message fails to send, invite cannot be copied, task update fails, or notifications cannot be marked read | Retry after the visible failure |
A failure message is not proof that the operation partially succeeded, so do not assume a new message, contact, or task was created.
Handle refusals and expirations
Some actions are intentionally refused instead of exposing more information. For example, a paused scheduled message can refuse to resume without saying whether it is unavailable, owned elsewhere, or tied to a conversation you cannot use. Keep it paused or return to the visible conversation context rather than guessing why it was refused.
Approvals can become already resolved or expired before you decide. Refresh the approvals list when either state appears. The original decision controls are no longer available for a request that has settled or expired.
A charge request without a displayed amount is treated as an error and does not show approval controls. Do not attempt to approve it through a different screen.
Check entry requirements
| State | Meaning |
|---|---|
| Sign-in prompt in developer space | Authentication is required |
| publisher-registration | Account has not yet registered a publisher |
| Empty list | Normal state for no notifications, no pending approvals, no connected contacts, or no scheduled messages |
These are entry requirements or normal states, not network errors. Follow the action offered on that screen when one is present. If the directory explicitly warns that its results may be incomplete, an empty filtered result is not a complete absence claim.