Claude 529 error handling

Hi ​@grachtdog 

Check the Anthropic Status page: https://status.anthropic.com/

Past incidents: https://status.anthropic.com/#past-incidents

These incidents impact the Zap runs.

Until Anthropic has a more stable API, your Zap runs will likely continue to experience these errors, regardless of what type of logic you try to implement to limit the errors.

Thanks ​@Troy Tessalone for your response. You may be right, but it is still a very unsatisfying answer. I guess I was hoping for better guidance on how I could use Zapier tools to better mitigate the Anthropic shortcomings. 

It is exactly this sort of challenge that makes Zapier a “fun AI project toy” for me to experiment with rather than a system that I might rely on to get actual work done.

​@grachtdog 

Zapier has an Auto Replay feature.

That can to auto retry failed Zap Run steps automatically up to 5 times.

Info: https://help.zapier.com/hc/en-us/articles/19220226086797-What-is-replay#h_01H9KBC1HMW07HTC6EC7NBTENH

​@grachtdog 

A different approach would be to use a queue.

Apps like these can be used for the queue:

• Zapier Tables
  • Counts as 0 Tasks in Zap Runs
• Airtable
• GSheets

Concept would be to log each record you want to process into the table.

Then have a different Zap that picks a record from the table queue and tries to process the record.

• If success, then delete the record and proceed to take the next record to process.
• If failure, then update the record with the encountered error, add a delay (e.g. 1 hour), and have the Zap trigger again.

Could have the Zap configured to run every hour.

Could have the Zap configured to fire from a webhook.

Could have the Zap configured to fire from some other app trigger event.

NOTE: Since Anthropic’s API can have variable reliability it may take 0-N retries to get a record successfully processed thru a Zap Run.

Cool. I will check these out. Thank you ​@Troy Tessalone !