Troubleshoot social queues, provider access and media processing
Use the existing receipt, connection health and worker evidence to identify the failing layer without exposing credentials or changing unrelated configuration.
Use these steps in your selected Pixie CRM company workspace. The module, dependent tools and actions available to you follow its configuration and your permissions.
Publishing activity; Social accounts; Configuration
PermissionRelevant viewing or management capability; administrator for worker inspection
Before you begin
Collect the workspace, provider, request reference, destination identity and approximate UTC time. Redact tokens, authorisation codes, secrets and private customer data.
Follow these steps
- Check the existing receipt to distinguish preflight, queued dispatch, provider processing and ambiguous delivery.
- Verify the connection and confirm the app has the required scopes, test users and provider approval.
- For media failures, check type, size, dimensions/duration, signed fetch access and any provider domain verification.
- Ask the administrator to check normal CRM cron execution and module activation if queued work or health checks are not advancing.
- Share the redacted request reference and exact error with support, along with the provider-side result already checked.
Fields and options
- Worker bounds
- Browser receipt dispatch advances a small bounded number of jobs; cron dispatch processes up to four queued jobs per pass.
- Asynchronous reconciliation
- Pending media jobs are checked within a bounded window of up to two days and 160 attempts, rather than indefinitely.
- Feature boundaries
- This interface provides Post Now, private drafts and receipts. It does not provide a future-date social scheduling calendar, X/Twitter posting, paid-ad buying or external AI generation.
Rules and limits
- Do not reset credentials merely because an individual post has invalid content.
- Do not manually reset an in-flight job to queued; this can duplicate an external write.
- Health/renewal maintenance is separate from the direct-publishing gate.
Check the result
- Confirm the repaired layer advances the existing eligible work as expected.
- Repeat a controlled new test only when the original outcome is known and the cause has been fixed.
If something does not look right
- For OAuth failures, compare callback, app credentials, account eligibility and provider consent.
- For unknown delivery, verify the provider account first; a healthy connection does not settle the earlier post’s outcome.
Common questions
Can I schedule a social post for next week here?
The current composer provides Post Now, not a future-date scheduling calendar.
Can support troubleshoot from a token screenshot?
Do not share tokens. Use redacted error text, request references, provider and UTC time instead.