Back to YQL Forum
0

Unable to process request at this time -- error 999

Hi, I'm running a little PHP script to find center lat/longs and bounding box for a given woeid from geo.places then shapefile data and Flickr URL for same from flickr.places. The script checks one woeid at a time and runs about every 10 seconds.

It ran fine for a while, say 45 minutes, then started returning an error HTTP/1.0 999 Unable to process request at this time -- error 999

After a while I ran the script again and it was OK for a while, then the same error message, wauted and ran the script again and now I have 'error 999' from geo.places bur no problem with flickr.places

I looked this up and apparently this is a special Yahoo error code used to prevent scraping and so on. Am I running the script too often or ??

by
Report Abuse
9 Replies
  • Hi Chaoley,

    This past post should help you better understand the 999 error that you are seeing: http://developer.yahoo.net/forum/index.php?showtopic=573

    - Jon
    Report Abuse
    0
  • QUOTE (Chaoley @ May 20 2010, 12:22 AM) <{POST_SNAPBACK}>
    Hi, I'm running a little PHP script to find center lat/longs and bounding box for a given woeid from geo.places then shapefile data and Flickr URL for same from flickr.places. The script checks one woeid at a time and runs about every 10 seconds.

    It ran fine for a while, say 45 minutes, then started returning an error HTTP/1.0 999 Unable to process request at this time -- error 999

    After a while I ran the script again and it was OK for a while, then the same error message, wauted and ran the script again and now I have 'error 999' from geo.places bur no problem with flickr.places

    I looked this up and apparently this is a special Yahoo error code used to prevent scraping and so on. Am I running the script too often or ??


    http://developer.yahoo.com/yql/

    Read the section on "Using YQL for Commercial and Non-Commercial Applications" where the Usage limits are specified.

    -balaji
    Report Abuse
    0
  • Hi Jon

    Thanks for that, looks like I'm not the only one experiencing this issue.

    I've set the JavaScript refresh delay to 10 seconds which seems to have solved the problem.

    Thanks
    John



    QUOTE (Jonathan LeBlanc @ May 20 2010, 12:08 PM) <{POST_SNAPBACK}>
    Hi Chaoley,

    This past post should help you better understand the 999 error that you are seeing: http://developer.yahoo.net/forum/index.php?showtopic=573

    - Jon
    Report Abuse
    0
  • Hi Balaji

    Thanks for the link, I notice two things that may be affecting the queries.

    1/ "Per IP limits: /v1/public/*: 1,000 calls per hour; /v1/yql/*: 10,000 calls per hour" - I'm currently using '/v1/public/', what's the difference between this and '/v1/yql/'? Can't find anything about it in the documentation.

    2/ "You may also be subject to the underlying rate limits of other Yahoo! and 3rd party web services" I suspect that this might be the issue as the error was sometimes coming from either geo or flickr, not always both.

    Regards
    John


    QUOTE (Balaji Narayanan @ May 20 2010, 06:18 PM) <{POST_SNAPBACK}>
    http://developer.yahoo.com/yql/

    Read the section on "Using YQL for Commercial and Non-Commercial Applications" where the Usage limits are specified.

    -balaji
    Report Abuse
    0
  • QUOTE (Chaoley @ May 20 2010, 11:24 PM) <{POST_SNAPBACK}>
    1/ "Per IP limits: /v1/public/*: 1,000 calls per hour; /v1/yql/*: 10,000 calls per hour" - I'm currently using '/v1/public/', what's the difference between this and '/v1/yql/'? Can't find anything about it in the documentation.


    http://developer.yahoo.com/yql/guide/authorization.html

    QUOTE
    2/ "You may also be subject to the underlying rate limits of other Yahoo! and 3rd party web services" I suspect that this might be the issue as the error was sometimes coming from either geo or flickr, not always both.


    Possible, you can check out those limits on their individual pages.

    HTH
    -balaji
    Report Abuse
    0
  • Looks like the way to go is with OAuth

    "The public URL has a lower rate limit than the OAuth-protected URL. Therefore, if you plan to use YQL heavily, you should access the OAuth-protected URL."

    Thanks for all the help, YQL seems worth spending the time on the learning curve.


    QUOTE (Balaji Narayanan @ May 21 2010, 03:06 AM) <{POST_SNAPBACK}>
    http://developer.yahoo.com/yql/guide/authorization.html



    Possible, you can check out those limits on their individual pages.

    HTH
    -balaji
    Report Abuse
    0
  • Hello, I had a text that read  that said something to the fact that there is an 999 error, so therefore my request cannot
    be completed. Can you please help me. I am not familiar with computer technical terms. So please, make it simple.
    Thank you .Glenda
    Report Abuse
    0
  • There have been some issues with our rate limiting system. If you notice 999 when coming here please try again in a few minutes.


    Thanks -Paul
    YQL Team
    Report Abuse
    0

  • error 999 for about 8 hours now... come on peops solve this problems maybe a better webdesign so we do not to get in and out for over 1000 times etc...

    Report Abuse
    0
Ask a Question

Recent Posts

in YQL