Public status page
Socializioz exposes a public status route at socializioz.com/status. Use it when several unrelated actions fail at the same time, the app is broadly unavailable, or you want to check whether a known service issue is already visible publicly. The public status page is the appropriate place for user-facing service-health information. This documentation intentionally does not hard-code a permanent list of status components, incident-history behavior, or recovery guarantees because those can change independently of the docs.Status is not the same as account health
A green public status page does not prove that every connected account or post is healthy. A problem can still be specific to:- One OAuth authorization or expired/revoked permission.
- One social account or provider capability.
- One workspace or role.
- One post’s media, approval, schedule, or publishing state.
- One external integration connection.
- One browser/device session.
Publishing incidents
Do not assume a failed or delayed provider action will automatically retry merely because a broad integration outage later recovers. Socializioz has explicit lifecycle and retry paths, and different provider outcomes can require different handling. Some work can remain processing; some failures can be retryable; others require reconnecting an account, correcting media, changing state, or taking an external action. When a publish fails:- Read the persisted post/publish state.
- Check the destination connection.
- Review the returned provider or validation error.
- Use the supported Retry, edit, reconnect, or reschedule path only when the current state allows it.
Admin health dashboard
Platform-level Socializioz administrators have an internal health function and dashboard that are separate from ordinary workspace roles. The current admin health function checks operational signals such as:- Backend/database reachability.
- Entity/activity metrics used for diagnostics.
- Connected social-token health.
- X realtime subscription state.
- Recent recorded errors.
- Presence of required backend configuration/secrets.
- Selected webhook/configuration checks.
How to investigate a suspected outage
1
Check the public status page
Open socializioz.com/status and look for a broad service issue.
2
Confirm your own connectivity
Make sure the device is online and reload the affected Socializioz surface.
3
Check the closest product state
Review Connections, Publishing Hub, Schedule, Activity Log, Billing, or the Agent result depending on what failed.
4
Avoid blind retries
If a provider write may still be processing, verify its current state before repeating the action.
5
Contact Support when the issue is account-specific or unclear
Include the workspace, platform, affected post or connection, approximate time, and returned error. Do not include passwords or raw access tokens.
What the docs do not guarantee
The system-status documentation does not promise that:- Every scheduled post is automatically replayed after a provider outage.
- A user’s current subscription can never be affected by a billing incident.
- Every provider or internal service has a separately displayed public status component.
- Status information is instantaneous.
- A public status page replaces the persisted state of an individual post, connection, or payment.