Two Bluesky API scripts hosted on totally different web hosts posting to totally different Bluesky accounts have stopped working. “Rate Limit Exceeded” The scripts weren’t doing much before this started, so it’s gotta be an issue on the @bsky.app end. Any idea @pfrazee.com? - ThreadSky

pdelahanty.bsky.social • 41 days ago

Two Bluesky API scripts hosted on totally different web hosts posting to totally different Bluesky accounts have stopped working. “Rate Limit Exceeded”

The scripts weren’t doing much before this started, so it’s gotta be an issue on the @bsky.app end.

Any idea @pfrazee.com?

Comments

nukeador.com•41 days ago

I can confirm same issue, calling createsession just once per hour I get rate limit error 429

"The service is receiving too many requests from you

RateLimitExceeded"

nukeador.com•41 days ago

The issue started around 12 hours ago for all the accounts I have some API automations.

mackuba.eu•41 days ago

Not sure if they changed the rate limit, but in any case, you shouldn't call createSession once an hour - store the tokens and call refreshSession if needed instead

nukeador.com•41 days ago

Ideally yes, but it's a running automation using n8n which I think doesn't save previous executions. I'll check 👌

n8n.io•41 days ago

Interesting - we're seeing this too, also for workflows that run every few hours. Could be an issue on their end, or alternatively you could store the session token externally and re-use?

nukeador.com•41 days ago

Definitely an issue on their end, not sure if a DDoS protection

@pfrazee.com

n8n.io•40 days ago

Our workflows seem to be running fine again today.

evertjan.at•41 days ago

Confirmed. I am seeing the same errors, starting a few hours ago.

pfrazee.com•41 days ago

What API endpoint is giving the error?

pdelahanty.bsky.social•41 days ago

com.atproto.server.createSession

pfrazee.com•41 days ago

Yeah you currently need to hold onto your tokens and use resumeSession or (iirc) refreshSession. create session has a low limit

pdelahanty.bsky.social•41 days ago

Was it recently lowered?

pfrazee.com•41 days ago

I just found out that it was, but also there was a bug and you can ignore my advice. A successful create session won’t get rate limited anymore (once our fix is out)

pdelahanty.bsky.social•41 days ago

Great! Thank you!
cc: @spokenlikeageek.com @cjr.dev

mackuba.eu•40 days ago

It seems to be affecting normal user logins too: https://bsky.app/profile/woj-tek.bsky.social/post/3lge75axonc2o

pthorton.bsky.social•41 days ago

I’m sure you are aware but the bots issue is not getting better. Of my 27 followers, 20 are most likely bots (they all follow 2-3k accounts and have less than 10 followers). It’s really annoying

adilson.net.br•40 days ago

Second time with one account and it gets a new token every 2 hours to avoid "Rate Limit Exceeded"

It worked nice until yesterday.

pdelahanty.bsky.social•40 days ago

Bug fix going out soon...

pfrazee.com•40 days ago

Should be out now

tenormad42.bsky.social•41 days ago

I was getting this error today, but it went away when I switched from logging in using username to using email address.

evertjan.at•41 days ago

It looks like replacing your handle with the email address for that account seems to work! \o/ At least with my first test cases.

pdelahanty.bsky.social•41 days ago

Well, it's been almost 24 hours since I first got the rate limit and I'm not getting it now. If I get it again later today, I'll try that fix. (Only made 3 API posts so far today...)

gbifmorpho.bsky.social•41 days ago

Happening for me too right now, fwiw

Comments

Posting Rules

Reply