Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

  • Home
  • Get Help
  • How Do I
  • I continually get error warning emails about my Xero zaps and when I check in they are fine, there are no errors in the log

I get errors like this regularly on various Xero zaps.

Xero: ExternalHTTPSConnectionPool(host='api.xero.com', port=443): Max retries exceeded with url: /api.xro/2.0/Payments?order=Date+DESC&where=Status%3D%3D%22AUTHORISED%22+AND+Date+%3E+DateTime%282020%2C11%2C09%29+AND+PaymentType%3D%3D%22ACCRECPAYMENT%22 (Caused by ConnectTimeoutError(<useful.request_extras.ExternalHTTPSConnection object at 0x7f1ce24e6f40>, 'Connection to api.xero.com timed out. (connect timeout=30)'))

When I check the task log all ran okay and there are no errors.

This only happens with Xero.

Its a huge time waster, does anybody else have similar issues?

Yes, I have the same issue also. Only started this ZAP today from a google sheet to Xero. Hopefully it is only a temporary issue with XERO. 

I’m getting this too - any way of getting around it? Do I have to reconnect / reauthorise anything? 

Its not a temporary thing unfortunately, it has been going on for a while with me.

 

Hello everyone, popping in here to let everyone know that a bug report has been filed for this issue and will have an ongoing investigation. Each of you in this topic has been added as an impacted user. We will reach out to you directly once this issue has an update.

Thank you!

Thanks, look forward to the update

Terms & Conditions