- Community
- Question
When I try to create or update a flow through the Graph API (which I've done many times in the past months successfully) I get the following error:
"Your message couldn't be sent because it includes content that other people on Facebook have reported as abusive."
Full error: error: {message: "Your message couldn't be sent because it inc…people on Facebook have reported as abusive.", type: 'OAuthException', code: 368, error_data: {…}, error_subcode: 1346003, …} code: 368 error_data: {sentry_block_data: 'AehgHK6mna1Ko5RH76j-K_F6dmy2Xp9iE38y34H…ob4pU43nMlXs61Y7BAoK_NlMMOZ0LNwqsV3AzHg', help_center_id: 0, is_silent: false} error_subcode: 1346003 error_user_msg: '' fbtrace_id: 'AWwi2rBSg8QP3lfVfZmQorV' message: "Your message couldn't be sent because it includes content that other people on Facebook have reported as abusive." type: 'OAuthException'
Check the callback url you are sending in the request. If it's ngrok or a similar one it'll be blocked by meta with that error code
The error indicates your content was flagged as abusive. To resolve this:
Check for and remove any potentially offensive or sensitive material.
Ensure your content follows Facebook’s Community Standards.
Reach out to Facebook Support with your fbtrace_id for detailed assistance.
Try posting simpler content to identify the problematic elements.
Manually test your API calls for more feedback.
I tried to create a test flow named "test_flow_2" - don't think there's anything offensive there. It let me add it through the FB Admin UI. so it seems like something is wrong on the API side.
@Yaniv - Any resolution for this? I too have the same issue.
Facebook Error Code 368, Subcode 1346003. The post might have been reported as abusive by Facebook users and therefore could not be published. Really useless and misleading error message for blocked image url. Check with sharing debugger if facebook blocked your Image URL. In my case the Image URL was on a Contabo S3 Bucket, which facebook blocked, but instagram not.