Keap Max Classic Authentications failing

This update concerns an incident that began on February 15th at 3:55 UTC. During this period, users experienced difficulties with Keap account connections which have now been resolved as of 6:26 PM UTC.

During the incident, there were reports of potential flood protection issues and frequent Keap connections expiring.

A communication will be sent out to all users who were impacted by this incident to guide them in checking their Zaps.

We encourage all users to reach out to our support if they continue to experience any issues: https://zapier.com/app/get-help

Our team has implemented a fix for the issue today at 6:26 PM UTC and has reconnected any stale Keap Max Classic connections. Your Keap Max Classic Zaps should now be running as expected.

You may see some residual errors in your Keap Max Classic actions from Zap runs that ran during the impacted time frame. In that case, you should be able to replay those Zap runs, and they should go through successfully.

Some Zaps using Keap Max Classic polling triggers could run into Flood Protection due to a large number of records being returned at once. To resolve this, you'll want to increase your Zap's Flood Protection by following the steps here:

https://help.zapier.com/hc/en-us/articles/32466537676685-Adjust-flood-protection-limits-in-Zaps

Once adjusted, you should be able to replay any held Zap runs using these instructions:

https://help.zapier.com/hc/en-us/articles/8496241726989-Replay-Zap-runs

If you have any further questions, please reach out to our support team here: https://zapier.com/app/get-help

We are currently investigating an issue where Keap Max Classic account connections have failed. The incident began on February 15th at 3:55 UTC and is ongoing.

Your patience is appreciated as we continue to seek a resolution to this issue. Further information will be shared as it becomes available.

For any additional questions, our support team can be contacted at: https://zapier.com/app/get-help.