Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8238205
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 7, 20262026-06-07T19:43:57+00:00 2026-06-07T19:43:57+00:00

Starting last Friday, 7/13, we’ve been getting the An unexpected error has occurred. Please

  • 0

Starting last Friday, 7/13, we’ve been getting the “An unexpected error has occurred. Please retry your request later.” error for our OG Graph object posts. With the same API post rate, our error rate for these API calls went from 0.13% to 65% (less than 1% to 65%) within about a minute. Saturday it dropped to about 46%, and it’s currently at 28%.

We normally have these automatically retried, but we had to disable that when the error rate rose because it choked our queue.

If we manually retry any of the failed ones, they fail every time with this error.

This seems to be happening only for one of our OG action/object combos – “earn medal”. All our other combos work fine with manual testing.

Since our error rate jumped suddenly, is very high, and retrying doesn’t work, something obviously seems wrong.

Could we be over a rate limit? Did something happen to our “medal” OG Object?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-07T19:43:58+00:00Added an answer on June 7, 2026 at 7:43 pm

    After some more manual testing, we realized this was only happening for a specific instance of our “medal” OG Object (id 4). Others worked fine. So we tried some of those instances (ids 1 through 5) in FB’s URL debugger, and they all parsed fine.

    Then tried to post those medals again manually, and id 4 then worked every time.

    It seems like FB automatically scraped our OG Objects last Friday, and the medal id 4 object request failed for some reason, causing that object’s cache to disappear on FB’s end.

    So if you see a sudden, large increase in OG Object API call errors, try manually re-caching the object instances that failed.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a live facebook application. Starting from last week, I keep getting PHP
Im testing latest 5.0 night builds and starting from last build R# installatior has
I spent the last 18 months getting the grip of functional programming, starting with
I'm starting up a new embedded system design using FreeRTOS. My last one used
Eclipse was running fine last night, but this morning I tried starting it up
I have a problem with starting the sunspot server. last week it worked like
I am trying to calculate last years starting day of the current week NOW()
I need to target the starting tag of the last top level LI in
I'm just starting to learn F#. I wrote this F#/ADO.NET code last night. In
I want to display the last 10 lines of my log file, starting with

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.