Troubleshooting

Start With the Activity Logs

Nearly every cross-posting problem is explained in the Activity Logs, which record the exact response from each service. Open the logs first — the specific API error there usually points directly at the fix.

Articles Are Not Being Cross-Posted

• Check the service is published.
• Check queue processing is active (Scheduled Task or page-load).
• Check per-article settings — Skip Cross-Posting may be enabled.
• Duplicate guard — articles are only cross-posted once per service.

Posts Are Failing

• Check Activity Logs for the specific API error.
• Expired tokens — re-authorize via the Connect button.
• Rate limits — the retry mechanism will handle these automatically.
• Invalid credentials — verify keys and permissions.

Twitter Posts Failing

• Ensure all four OAuth 1.0a keys are filled in.
• Bearer tokens cannot create tweets.
• Ensure Read and Write permissions in the Developer Portal.

Queue Is Not Processing

1. Check System → Scheduled Tasks — is the task enabled?
2. Verify processing method in component options.
3. Check PHP error logs.

A Quick Checklist Before You Ask for Help

1. Is the target service published?
2. Is the account still connected (tokens not expired)?
3. Did the article meet the trigger conditions (published, not previously posted)?
4. What does the Activity Log entry say for that article and service?

Still Stuck?

If you have checked the logs and the items above and the problem persists, contact the Moko Consulting team at This email address is being protected from spambots. You need JavaScript enabled to view it. with the relevant Activity Log entry so we can help quickly.