TROUBLESHOOTING
Maintained DivisionDesk documentation · Updated 2026-08-21
# Troubleshooting
- **401/403:** reconnect the account and verify app approval, scopes and account/Page roles.
- **429:** wait for the provider rate-limit window; the scheduler should defer retry.
- **Instagram text-only error:** add media or deselect Instagram.
- **TikTok/YouTube public publishing unavailable:** verify developer-app review/audit status.
- **Button appears stuck:** fetch handlers restore buttons in `finally`; check for third-party JavaScript errors if a custom script interrupts the page.
- **Unexpected crop:** review the per-platform derivative/preview and choose another crop before publishing.
## Duplicate registry error during module update
Social Media 1.0.7 and later make module registration idempotent within one PHP request. DivisionDesk Core may already have the installed module booted when an Update action replaces the package files. Because PHP retains the already-loaded class until the request ends, Core can invoke that same class's `register()` again. Social Media ignores that repeated call and the next HTTP request boots the newly installed version normally.
- **401/403:** reconnect the account and verify app approval, scopes and account/Page roles.
- **429:** wait for the provider rate-limit window; the scheduler should defer retry.
- **Instagram text-only error:** add media or deselect Instagram.
- **TikTok/YouTube public publishing unavailable:** verify developer-app review/audit status.
- **Button appears stuck:** fetch handlers restore buttons in `finally`; check for third-party JavaScript errors if a custom script interrupts the page.
- **Unexpected crop:** review the per-platform derivative/preview and choose another crop before publishing.
## Duplicate registry error during module update
Social Media 1.0.7 and later make module registration idempotent within one PHP request. DivisionDesk Core may already have the installed module booted when an Update action replaces the package files. Because PHP retains the already-loaded class until the request ends, Core can invoke that same class's `register()` again. Social Media ignores that repeated call and the next HTTP request boots the newly installed version normally.
Still need help? Search the Community for real-world discussion, or submit a Feature Request if the product itself needs to change.