Hey everyone,
I’ve been running a stable automation for posting Facebook Stories via Graph API, but now I’m getting a new intermittent error during the “upload video file” step:
Forbidden - perhaps check your credentials? (403 -
"{\"debug_info\":{
\"retriable\":false,
\"type\":\"ProcessingFailedError\",
\"message\":\"{\\\"success\\\":false,
\\\"error\\\":{
\\\"message\\\":\\\"Supplied user is not the creator of this video 1271066478114057\\\"
}
}\"
}}")
Important context
This automation uses the official Graph API upload flow:
1. start upload → 2. upload chunks → 3. finish publish
-
I choose the access token before starting the upload session.
-
The same access token is passed into all three API calls.
-
My workflow is designed so the token cannot change during the 3-step upload, because:
-
token selection happens before Start Upload Session
-
Start Upload Session, Upload File, and Publish Story all use the same
$json.access_token -
token rotation happens only after a story is fully published, never mid-process.
-
The problem
Even though the token cannot change mid-upload, Facebook sometimes returns:
“Supplied user is not the creator of this video.”
This error suggests that the token used for “start session” and “finish publish” does not match — but in my workflow the value is static across all steps.
And what makes this even more confusing:
the exact same workflow publishes several stories successfully, and then suddenly throws this error, even though nothing changes in the workflow between successful and failed items.
So the workflow logic is identical across all items, but Facebook only complains randomly.
If anyone has experienced something similar or knows how to guarantee identical token reuse inside the same item chain, I’d really appreciate your insights.
Thanks!
