Hi there @Semast,

Before we dig deeper into this, have you tried replaying the failed run of your Zap? Check out this helpful article we have on replaying errored runs: https://help.zapier.com/hc/en-us/articles/8496241726989

Keep us posted! 
 

I can do it of course but there is no sense to replay zap manually every time I have such error.

@Semast I certainly understand that point of view. 

Can you please tell us a bit more about when you encounter these errors? Do you notice any patterns such as an influx of data or after a # of runs? 

Another thing that will be beneficial in us getting this resolved is any screenshots you may be able to provide of your Zap setup? Of course, please omit any personal or identifying information when posting! 

Hi @Semast!

I dug into this a bit and haven’t found anything super conclusive. I see an error message that indicates we received a 429 HTTP response from Medium.

The HTTP 429 Too Many Requests response status code indicates the user has sent too many requests in a given amount of time ("rate limiting").

Source.

Do you by any chance have multiple Zaps trying to do the same thing with Medium? 

To be honest, there is nothing to say more We post around 2-4 articles a week and sometimes we have such error. No pattern no regularity nothing.

Screenshot:

Nope, I have only 1 zap at all :(

Hi @Semast,

It looks like you may be encountering a rate-limiting error on Medium's end which should be temporary. One troubleshooting step you can try is to recreate the Zap to see if the issue persists.

Please keep us posted!