Issue Summary

Zapier Confluence integration times out with 403 error when triggering the event

This is reproducible on Data Center: n/a

Steps to Reproduce

Customer is using Zapier app integration with Confluence (not an app from Marketplace): https://zapier.com/apps/confluence-cloud/integrations

1. Zapier sends user an email with "Trigger partner failure: Response with status code 403".
2. User clicks "Fix My Zap".
3. User sees the error: you need to connect a confluence account.
4. User connects his account. The Zap runs. And then Zapier disconnects from Confluence hours/days later.

Expected Results

Connect cap without any error to trigger the event

Actual Results

Throws 403 timeout error

Other Notes

• Error notes from Zapier: https://community.zapier.com/general-questions-3/repeated-this-account-is-expired-confluence-errors-14259
• Community article: https://community.atlassian.com/t5/Confluence-questions/Confluence-Cloud-connection-to-Zapier-times-out/qaq-p/1971376
• Zapier says the issue is with the Confluence Cloud integration owned by Atlassian. We are being impacted by Issue # 16 in Zapier's internal reporting tool.

  From Zapier support:
  "Most integrations on Zapier are developed and maintained by the App Owners themselves. (There is a small group that we are responsible for directly).

  The Confluence Cloud integration is developed and maintained by Atlassian directly - meaning they would be the team that fixes any bugs.

  When there are bugs or feature requests for an integration - we open a request through an internal tool which enables us to communicate with the developer of the integration.

  And we'll add your email to that request so we can notify you when it is resolved...

  Taking a quick look at this one - I don't see any update from Atlassian.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available