Overview
This article provides the steps to resolve a high-priority workflow failure caused by a security lockdown on the linked Meta/Facebook account. This error blocks automated workflows because the connection requires manual human intervention to clear a checkpoint.
The core issue is not an expired credential, but an active security challenge on the Meta account linked to the Amperity application.
Symptoms and Root Cause
| Symptom You See | Underlying Error Code | Root Cause |
|---|---|---|
| Workflow stops immediately. |
HTTP Error 401 (OAuthException) |
The Facebook account owner must manually log in to the associated Facebook account to clear a security challenge (e.g., confirming identity, accepting new terms). |
| Error Message | "You cannot access the app till you log in to www.facebook.com and follow the instructions given." | The system is requesting human intervention to clear a security checkpoint (error_subcode 459) that is blocking the API token. |
| Customer Report | "We are not seeing anything Amperity related when we log in." | The security prompt is often generic (e.g., "Confirm recent activity") and does not mention Amperity, but it must be resolved before the API token is unblocked. |
Required Action: Clearing the Security Checkpoint
The owner of the Facebook account linked to the Meta CAPI connection must take the following steps:
Step 1: Log In Manually
The person who initially authorized the Amperity CAPI connection must:
Log into Facebook directly in a standard browser window (not incognito) using the exact same credentials linked to the account.
Step 2: Clear the Security Prompt
Once logged in, they must follow any on-screen instructions, prompts, or notifications (often in the notification bar or Security Settings) to clear the security checkpoint and verify the account's status.
Step 3: Re-run the Orchestration
After the checkpoint is definitively cleared on the Facebook side, re-run the scheduled orchestration in Amperity. The workflow should now successfully authorize and send the data.
Note: If the issue persists after clearing the checkpoint, the authorization token may have been revoked entirely, and the credential will need to be re-authorized in Amperity.