Amplify troubleshooting for social posting issues

Diagnosis steps and fixes for common Amplify publishing issues across social networks.

All issues documented in this guide, grouped by network:

Network	Documented issue
Any	• Link previews missing on social networks
Meta (Facebook, Instagram, and Threads)	• Error 613: API rate limit exceeded • Meta account activity restrictions (codes 368/1404112, 1/2424009, 1/2207051) • Facebook flagging comments as spam • Instagram “Suspicious Activity Detected” notifications
TikTok	• Custom thumbnails not accepted • Rate limit: HTTP 403 spam_risk_too_many_posts
WhatsApp	• Integration disconnection

How Amplify recovers from invalid sessions and rate limits

Amplify monitors each connection for two API-side conditions and reacts automatically, so publishing keeps moving without manual intervention.

Invalid session

When a network rejects the stored session, Amplify triggers the reconnect flow for that feed. The owner is prompted to sign in again to restore the connection. Common triggers: a password change or revoked Amplify access.

Rate limit errors

When a network returns a rate limit error, Amplify pauses publishing on the affected account for 1 hour before retrying. The pause gives the network time to clear the throttle and prevents repeated requests from escalating the restriction.

Link previews missing on social networks

Social networks fetch metadata directly from your site when you share a link. Amplify does not control this process. If the preview image or metadata (title, description) does not appear on Facebook, X, or LinkedIn, the problem is between the platform’s crawler and your server.

Common causes

• Missing or invalid Open Graph tags (og:image, og:title, og:description)
• robots.txt blocking the platform’s crawler
• Server blocking the crawler (e.g. 403 Forbidden)
• Cached or outdated data on the social platform

How to diagnose

Test with the exact URL Amplify would publish, not the clean article URL. Amplify appends query parameters for tracking, and some servers or CDNs handle parameterized URLs differently (redirects, blocks, stripped metadata). If you test only the base URL, you might miss the actual problem.

Amplify URLs follow this pattern:

https://example.com/article-slug/?utm_campaign=mrf-facebook-feedname&mrfcid=20260305...

Paste the full parameterized URL into the platform’s diagnostic tool:

Platform	Diagnostic tool	What to look for
Facebook	Sharing Debugger	Warnings, errors. Use Scrape Again to refresh.
X	Card Validator	Confirm og: tags are rendering correctly
LinkedIn	Post Inspector	If you see “We can’t access this content. It may be blocked by robots.txt”, the crawler is blocked

Fix crawler blocks in robots.txt

Each social network uses its own crawler to fetch link previews. If your robots.txt blocks any of them, previews will fail on that platform. Add the following rules to allow all social crawlers:

# Facebook (link previews and product catalogs)
User-agent: facebookexternalhit
Allow: /
User-agent: facebookcatalog
Allow: /

# X / Twitter (Twitter Cards)
User-agent: Twitterbot
Allow: /

# LinkedIn (links shared in posts, messages)
User-agent: LinkedInBot
Allow: /

# WhatsApp (chat previews, uses Facebook infrastructure)
User-agent: WhatsApp
Allow: /

# Pinterest (Rich Pins)
User-agent: Pinterest
Allow: /

# Telegram (chat previews)
User-agent: TelegramBot
Allow: /

# Reddit (post and comment previews)
User-agent: redditbot
Allow: /

# YouTube / Google (embedded link previews, also used for search indexing)
User-agent: Googlebot
Allow: /

After updating your robots.txt:

1. Use each platform’s diagnostic tool (see table above) to confirm the crawler can now access your pages
2. Click Scrape again or equivalent refresh option to clear cached data
3. Confirm your og:image tag points to a valid, accessible image
4. For LinkedIn specifically, verify the image meets LinkedIn’s requirements: minimum 1200 x 627 px, under 5 MB

Quick workaround

Switch Amplify to Photo mode instead of Link Preview. Amplify hosts the image directly, so it displays regardless of crawler issues while you resolve the underlying problem.

Meta (Facebook, Instagram, and Threads)

Recommendation: Connect multiple Meta users to your Amplify integration. When one Meta user becomes unavailable due to a rate limit, account block, or invalid connection, Amplify automatically fails over to another connected user. The more Meta users you have connected, the more resilient your publishing setup is.

Error 613: API rate limit exceeded

This error appears when the app exceeds Meta’s API rate limits, typically after changes to posting frequency or feed volume. Amplify emails the user who originally connected the affected feed.

From Meta’s documentation:

“Indicates that we have noticed inconsistent behavior in the API request volume of your app. If you have made any recent changes that affect the number of API requests, you may be encountering this error.”

How to fix:

1. Connect a different Meta user. The rate-limited user remains restricted by Meta. Add a new integration using a different Meta user to resume publishing immediately.
2. Reduce posting volume for a few days. If you recently changed your posting schedule or added new feeds, the combined volume may exceed Meta’s thresholds. Manage schedules from your Amplify settings.

Meta account activity restrictions

Meta applies account-level activity restrictions to the connected user when posting through the Graph API. Triggers include posting frequency, repetitive content, reused creatives, or activity that Meta’s automated systems classify as a Community Standards violation. The restriction typically clears in 24 hours to a few days, and the affected user can review and appeal it from Facebook’s Account Status page.

The same family of restriction surfaces in Amplify logs with three different error signatures, depending on the Meta surface that triggered it. The user-facing message comes localized in the Meta user’s account language.

Code 368, subcode 1404112 — Facebook security-related limitation:

Media upload error, com.restfb.exception.FacebookOAuthException:
Received Facebook error response of type OAuthException:
For security reasons, your account will have limited access to the site
for a few days. (code 368, subcode 1404112)

Code 1, subcode 2424009 — Facebook/Instagram active account restriction:

An unknown error occurred (code 1, subcode 2424009)
'This action is restricted for your account - Your account has an
active restriction that prevents you from completing this action.
If you believe this is a mistake, you can appeal through the
"Account Status" page.'

Code 1, subcode 2207051 — Threads activity restriction:

An unknown error occurred (code 1, subcode 2207051)
'Action blocked - We restrict certain activity to protect our
community. If you think we have made a mistake, let us know.'

Important: The block is tied to the Meta user, not to the token. Reconnecting the integration or refreshing the token does not resolve it. Confirm by logging into facebook.com or threads.net with the affected Meta user, the same restriction message will appear there.

Fix: Fail over to a different Meta user. Amplify publishes through the backup user until Meta lifts the restriction on the original one.

Facebook flagging comments as spam

Facebook’s anti-spam system flags repetitive comments. To avoid this, include dynamic text in your comments: the article’s og:title, og:description, or Marfeel Copilot prompts. Dynamic elements make each comment unique and more engaging, keeping you clear of spam detection.

If your feed is already flagged

Action	Why it helps
Stop posting comments for a few days	Resets Facebook’s spam detection
Reduce posting frequency when you resume	Avoids re-triggering thresholds
Review recent posts for repetitive content	Identify patterns that triggered the flag
Avoid catchy, repeatable titles like “the 10 most XX”	Facebook recognizes clickbait patterns
Vary structure and phrasing across articles	Breaks repetition signals, even when using similar templates

Instagram “Suspicious Activity Detected” notifications

Instagram may flag automated activity as suspicious. For detailed diagnosis and resolution steps, see the dedicated troubleshooting guide.

TikTok

Custom thumbnails not accepted

TikTok’s API does not accept image files as custom video covers. Only frames extracted from the video itself can be assigned as the thumbnail. This is a TikTok platform restriction, not an Amplify limitation. No setting can override it.

To set a specific visual as the cover:

• Pick the frame in Amplify. During upload, choose a frame from the video timeline as the cover.
• Edit the video so the desired image appears at the start. If you need a branded intro card or specific shot, embed it as the opening frame of the video file. TikTok will then offer it as a selectable cover.
• Update the cover natively in TikTok. TikTok’s mobile app allows uploading a custom cover image directly. Publish through Amplify, then edit the cover from the TikTok app.

Rate limit: HTTP 403 spam_risk_too_many_posts

TikTok returns HTTP 403 with the code spam_risk_too_many_posts when an account exceeds its daily posting threshold. TikTok is intentionally vague about the exact limit; in practice the threshold sits between 15 and 25 posts per day per account. If you hit this regularly, reduce the daily volume on the affected account or distribute posts across additional connected accounts.

WhatsApp integration disconnection

The WhatsApp integration may disconnect unexpectedly. This is triggered by changes on the connected device. If it disconnects, you need to reconnect your feed to resume functionality.

Known causes

• Device unlinked explicitly from the mobile phone
• Phone not connected for 14 consecutive days
• Exceeding the maximum of 4 linked devices per feed

The Amplify integration is identified as Firefox on Ubuntu in your WhatsApp linked devices list:

Important: WhatsApp's exact disconnection criteria are not fully transparent. Additional cases may occur beyond those listed above. If the integration disconnects, you need to reconnect it to resume functionality.

Why are link previews missing when Amplify shares to social networks?

Social networks fetch metadata directly from your site, not from Amplify. Missing previews are usually caused by invalid Open Graph tags, robots.txt blocking the platform’s crawler, server errors like 403 Forbidden, or cached outdated data. Test with the exact parameterized URL Amplify publishes using each platform’s diagnostic tool.

How do I fix Meta API rate limit error 613 in Amplify?

Error 613 means your app has exceeded Meta’s API rate limits. Connect a new integration using a different Meta user to resume publishing immediately, then slow down posting for a few days. To prevent future rate limits, connect multiple Meta users. Amplify automatically fails over to another user if one becomes rate-limited or invalid.

What do Meta errors 368/1404112, 1/2424009, and 1/2207051 mean in Amplify?

All three error signatures are account-level activity restrictions applied by Meta to the connected user, not by Amplify. Code 368 subcode 1404112 surfaces as a Facebook security-related limitation, code 1 subcode 2424009 as a Facebook/Instagram active account restriction, and code 1 subcode 2207051 as a Threads activity restriction. The cause is the same across all three: automated systems flagged the user for abuse signals such as repetitive media uploads, reused creatives, or activity that violates Community Standards. The restriction usually clears in 1 to 7 days. Switch to a backup Meta user to keep posting while the block is active, and reduce posting cadence when access returns. The affected user can appeal from Facebook’s Account Status page.

Why does the WhatsApp integration keep disconnecting from Amplify?

WhatsApp disconnects when the linked device is removed from the mobile phone, when the phone is not connected for 14 consecutive days, or when you exceed the maximum of 4 linked devices per feed. The Amplify integration appears as Firefox on Ubuntu in the WhatsApp linked devices list.