I'm seeing inconsistent responses from the Page Blocked endpoint when attempting to block users by PSID. Specifically I'm able to block some users successfully while others return the error response:

{
  "error": {
    "message": "(#100) Invalid parameter",
    "type": "OAuthException",
    "code": 100,
    "fbtrace_id": "AqgawKrSbbaHGT7HT016Gpd"
  }
}

I'm using the same access token across all of the requests and I'm able to retrieve the user who cannot be blocked by PSID from the graph session without issues. This issue is blocking our customers from blocking users within the sprout app.

Including Saved Graph Sessions, the facebook page is called "Eat Bacon" and it's ID is 1656957550981542 * Session retrieving all blocked users for Eat Bacon account * https://developers.facebook.com/tools/explorer/331741700416/?session_id=540928055504801 * Session where I blocked the user Earl Scout successfully(8982583745131907) * https://developers.facebook.com/tools/explorer/331741700416/?session_id=1128228859021963 * Session where I was unable to block user Nick Cole (7843315795753926) * https://developers.facebook.com/tools/explorer/331741700416/?session_id=445119528625763 * Session retrieving user details about user Nick Cole to demonstrate user exists (7843315795753926) * https://developers.facebook.com/tools/explorer/331741700416/?session_id=888386910135648

I see that the error code 100 is mentioned in the documentation as Invalid Parameter, but this behavior seems like a bug to me. I'm using the same formatting and access token between the successful and failing API calls to the blocked endpoint with the only difference being the actual PSID value being passed in.

Link to relevant documentation: https://developers.facebook.com/docs/graph-api/reference/page/blocked/