Skip to main content
Start with the area where the problem appears, then use the returned error and current post or account state to decide the next action.

Quick checks

1

Confirm the app and connection

Check your internet connection, refresh the page, and confirm the correct workspace is active.
2

Check connected accounts

Open Connections and reconnect any account showing an authorization or permission problem.
3

Open the affected item

Use Publishing Hub, the calendar, or the Composer to inspect the failed post and its returned error.
4

Check plan availability

Review Plans and billing when a platform, integration, or feature is locked.
5

Check platform requirements

Confirm the account, media type, dimensions, schedule, timezone, and platform-specific settings.
6

Escalate with context

Contact Support with the affected account, post, time, platform, and visible error.

Sign-in and app loading

Socializioz requires an internet connection for normal use. Scheduled publishing runs through backend services and does not require the browser to remain open.

Connection problems

Publishing failures

A failed post remains available for review. Open it from Publishing Hub or the calendar and use the returned error to choose the fix. Use Retry only after correcting the cause. Rescheduling without fixing an account, permission, or media problem can produce the same failure again.

Plan limits

When a metered limit is reached, the affected action can be blocked until the billing cycle resets or the workspace upgrades. Connected social accounts are unlimited on all current plans. Platform availability still depends on the plan. There is no documented 72-hour grace period. Use the usage shown in Billing as the current source for your workspace.

AI generation problems

Current video generation uses Google Veo 3 with supported 4, 6, or 8 second durations and 9:16 or 16:9 formats.

Mobile and browser problems

Use a current version of Chrome, Safari, Edge, or Firefox. On mobile, keep the Socializioz app updated through the App Store or Google Play. When troubleshooting a native-app issue, separate these cases:
  • The same action works in the mobile browser but fails in the installed app.
  • The issue affects only Android or only iOS.
  • The issue occurs only during provider authorization.
  • The issue appears after changing system text size, display scaling, or browser privacy settings.
These details help Support identify whether the problem is in the web app, native shell, provider authorization, or device environment.

Permanent actions

Deleting accounts, workspaces, posts, campaigns, or media can be permanent. Review the confirmation message and export anything you need before deletion. Do not assume every deleted item can be restored.

Contact Support

Include:
  • The affected workspace.
  • Platform and account.
  • Page or feature.
  • Exact time and timezone.
  • Visible error text.
  • Whether it happens on web, iOS, Android, or all of them.
  • A screenshot when it does not expose private credentials.
Last modified on July 22, 2026