Is Zapier Down Right Now? Check if there is a current outage ongoing.

Customers have reported a range of issues related to app authorizations, with a specific emphasis on authorizations related to Google integrations. We appreciate your patience as we investigate these issues.

We are currently investigating an issue where Zapier Tables is returning an error after accessing a Table URL directly. Our Team has identified the issue and we'll provide an update as soon as it's resolved.

We are receiving reports related to Pipedrive triggers failing. This is related to an incident from Pipedrive that is now resolved. However, we are continuing to monitor these issues. Please let us know if you continue to run into triggers failing: https://zapier.com/app/get-help

We've identified an issue where Zapier accounts are being automatically switched, returning "Unable to access Zap" and " You either don't have permission to see this Zap or the Zap does not exist" errors. This switch occurs between accounts users already have access to, but it is causing disruption while using the Zapier interface. We're currently working to implement a fix to address this issue and will update the StatusPage as soon as there are relevant updates. There appears to be no risk of data loss at this time. If you have further questions, please reach out to our Support Team here: https://zapier.com/app/get-help

We're currently investigating an issue that is impacting Functions. Updating existing Functions and creating new ones is causing them to fail silently and not execute as expected. Existing Functions that are have not been updated are continuing to work as expected. Our team has identified the issue, and we'll provide an update as soon as we know more and it is resolved.

We’re currently investigating an issue causing delays in some Zap runs and slower performance across the platform. Affected users may experience longer execution times or missing steps in Zaps. You may also notice delays in Zap history updates. Our Team has identified the issue, and we'll provide an update as soon as it's resolved.

During this maintenance window, some users may experience delays with webhooks, and Zapier.com may return 502 (Bad Gateway) or 503 (Service Unavailable) errors. We expect a minimum downtime of 30 minutes, however this behavior may last up to 90 minutes.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Starting at 15:01 UTC, we were alerted to errors with internal tooling used to monitor Zaps. This was preventing the ability to view internal Zap request logs, specifically in the Developer Portal and UI. Our team has since released a fix for this issue and functionality has returned. If you run into any issues regarding this feel free to reach out to our Support team directly.

Starting at 15:01 UTC, we were alerted to errors with internal tooling used to monitor Zaps. This was preventing the ability to view internal Zap request logs, specifically in the Developer Portal and UI. Our team has identified and implemented a possible fix, and we are currently monitoring results to determine full efficacy. We will update this page with the final resolution once confirmed!

Starting at 15:01 UTC, we were alerted to errors with internal tooling used to monitor Zaps. This is preventing the ability to view internal Zap request logs. This currently only impacts the Developer Portal and UI. Our team is currently investigating the root cause and hope to have a fix available soon. You can subscribe to this page for update. For any other questions, please feel free to contact our Support Team at https://zapier.com/app/get-help.

This incident has been resolved. Find/Search actions should now provide fields to map other actions steps in the Zap.

Our Engineering team have identified the source of the issue and implemented a fix. Now, all Find and Search actions should return the expected fields. We are monitoring this to ensure the issue has been resolved for all users.

We're currently investigating an issue that is causing Find/Search actions to not return the expected output fields in the Zap Editor. Our Engineering team is actively investigating this issue, and we will provide more updates as soon as possible. We really appreciate your patience while we work through this!

We're currently investigating an issue that is causing Find/Search actions to not return the expected output fields in the Zap Editor.Our Engineering team is actively investigating this issue, and we will provide more updates as soon as possible.We really appreciate your patience while we work through this!

This incident has been resolved. All Zap runs that failed with this error have been replayed. For any other questions, please feel free to contact our Support Team at https://zapier.com/app/get-help.

The issue has been identified and a fix is being implemented.

We have received a number of reports from users that are seeing the following error for Webhooks by Zapier steps in their Zaps: "value.replace is not a function" We believe this may be due to a regression issue following a recent version update. Our team is currently investigating the root cause of this error and what steps may be necessary to revert to working functionality again. You can subscribe to this page for updates.

Earlier today (May 20th), our systems in the Developer Portal/UI encountered a tooling issue that prevented the ability to review request logs. Our team was able to identify the necessary fix, and this issue has now been resolved. Thank you for your understanding and patience as we worked on this!

Starting at 4:20 PM UTC, we were alerted to errors with internal tooling used to monitor Zaps. This was preventing the ability to view internal Zap request logs, specifically in the Developer Portal and UI. Our team has identified and implemented a possible fix, and we are currently monitoring results to determine full efficacy. We will update this page with the final resolution once confirmed!

Starting at 4:20 PM UTC, we were alerted to errors with internal tooling used to monitor Zaps. This is preventing the ability to view internal Zap request logs. This currently only impacts the Developer Portal and UI. Our team is currently investigating the root cause and hope to have a fix available soon. You can subscribe to this page for update. For any other questions, please feel free to contact our Support Team at https://zapier.com/app/get-help.

We have received a number of reports from users that are seeing the following error for Webhooks by Zapier steps in their Zaps:"value.replace is not a function"We believe this may be due to a regression issue following a recent version update. Our team is currently investigating the root cause of this error and what steps may be necessary to revert to working functionality again. You can subscribe to this page for updates.

Starting at 4:20 PM UTC, we were alerted to errors with internal tooling used to monitor Zaps. This is preventing the ability to view internal Zap request logs. This currently only impacts the Developer Portal and UI. Our team is currently investigating the root cause and hope to have a fix available soon. You can subscribe to this page for update. For any other questions, please feel free to contact our Support Team at https://zapier.com/app/get-help.

The incident re-commenced at 10:44 PM UTC and was resolved by 00:06 AM. During this period, users would have experienced failures and errors in many of their Zaps across several apps. The specific error message displayed was "Object of type datetime is not JSON serializable." Fortunately, this issue has been addressed and resolved completely. Now, the errored tasks are being replayed, and no additional action is required. We're pleased to inform you that there has been no data loss associated with this incident. All tasks are securely being replayed, and it is expected that future runs will not encounter any similar issues. We understand the inconvenience caused during this period. If you still experience issues, we encourage you to contact our Support Team through this link: https://zapier.com/app/get-help We appreciate your patience during this time. Thank you.

We're currently investigating an re-occurance of a previously issue causing some API responses to fail with the error: "Object of type datetime is not JSON serializable." Please do not hesitate to reach out to us if you experience further issues. Please contact our Support Team here: https://zapier.com/app/get-help

We're currently investigating an re-occurance of a previously issue causing some API responses to fail with the error: "Object of type datetime is not JSON serializable." Please do not hesitate to reach out to us if you experience further issues. Please contact our Support Team here: https://zapier.com/app/get-help

We experienced a brief issue today starting at 6 PM (UTC). Some Zap runs failed with the error "Object of type datetime is not JSON serializable." Our team quickly identified the problem and implemented a fix. All affected Zap runs have been successfully replayed. Thank you for your patience as we resolved this. If you have any questions or notice anything unusual, please don’t hesitate to contact us at https://zapier.com/app/get-help.

Our team identified the issue and has implemented a fix. We’re now in the process of replaying any affected Zap runs that encountered the error. Thank you so much for your patience while we worked through this. If you have any questions or notice anything unusual, feel free to reach out to Zapier Support here: https://zapier.com/app/get-help.

We’re currently investigating an issue causing some API responses to fail with the error: Object of type datetime is not JSON serializable. Please do not hesitate to reach out to us if you experience further issues. Please contact our Support Team here: https://zapier.com/app/get-help

We’re currently investigating an issue causing some API responses to fail with the error: Object of type datetime is not JSON serializable.Please do not hesitate to reach out to us if you experience further issues. Please contact our Support Team here: https://zapier.com/app/get-help

We’ve identified that the error affecting recovery code regeneration for 2FA is limited to a small number of accounts and does not appear to be caused by a broader system failure. As a result, we’re no longer treating this as a widespread incident, but our engineering team is actively working on it as a high priority bug. If you encounter this issue, please reach out to our support team for assistance: https://zapier.com/app/get-help

We are investigating an issue related to an error when regenerating 2FA recovery codes. Our engineers are actively looking into this. We will update the status page as we find out more!

The previously reported issue where Zapier Agents were experiencing a 500 error has been resolved. Our Engineering team has successfully addressed the problem, and all systems are now operating normally. We appreciate your patience and understanding during this time. If you continue to experience any issues, please reach out to our support team.

We have identified the cause of that issue with Agents and MCP not loading, and have pushed a fix. We are currently monitoring our update to confirm that it has resolved this issue. We will follow up here with more updates once we have confirmed that this issue issue is resolve. Thanks again for your patience!

We are currently investigating an issue where Zapier Agents is unable to load and returning a 500 error. Our Engineering team is actively investigating this issue, and we will keep this status page updated as we learn more insights into the issue. We really appreciate your patience while we work through this!

We are investigating an issue related to an error when regenerating 2FA recovery codes. Our engineers are actively looking into this. We will update the status page as we find out more!

We are currently investigating an issue where Zapier Agents is unable to load and returning a 500 error.Our Engineering team is actively investigating this issue, and we will keep this status page updated as we learn more insights into the issue.We really appreciate your patience while we work through this!

We’ve resolved the issue that was affecting Slack Triggers, where some output fields were not being returned as expected, leading to missing data errors in some Zaps. An updated version of the Slack app caused the issue. We have rolled back to the previous version and migrated affected customers, which has restored full functionality. Thank you for your patience while we worked to resolve this. If you require additional assistance, please feel free to reach out via our Support page: https://zapier.com/app/get-help.

We are currently investigating an issue where Slack Triggers functionality is affected. Some output fields are not being returned as expected, resulting in missing data errors for some Zaps. Our Engineering team is actively investigating this issue, and we will keep this status page updated as we learn more insights into the issue. We really appreciate your patience while we work through this! If you require additional assistance, please feel free to reach out via our Support page: https://zapier.com/app/get-help.

We are currently investigating an issue where Slack Triggers functionality is affected. Some output fields are not being returned as expected, resulting in missing data errors for some Zaps. Our Engineering team is actively investigating this issue, and we will keep this status page updated as we learn more insights into the issue.We really appreciate your patience while we work through this! If you require additional assistance, please feel free to reach out via our Support page: https://zapier.com/app/get-help.

We are delighted to inform you that the issue has been fixed and users should now be able to access the community pages without any issue as we speak. The incident started at 19:44 UTC and was resolved by 20:08 UTC. During this period, users reported encountering an error message when trying to access Zapier Community pages. The specific error message was of type 400 or 500. We appreciate your understanding and patience during this incident. Apologies for any inconvenience caused. Please do not hesitate to reach out to us if you experience further issues. Please contact our Support Team here: https://zapier.com/app/get-help

Accessing pages in the community are no longer returning an error. We will continue to monitor the situation and we'll provide an update as soon as we can. If you need immediate help, please reach out to our Support team:https://zapier.com/app/get-help

Our team is currently investigating an issue with Zapier Community returning a 404 or 500 error when attempting to access posts within the Community. We'll provide an update as soon as we can. If you need immediate help, please reach out to our Support team: https://zapier.com/app/get-help

Our team is currently investigating an issue with Zapier Community returning a 404 error when attempting to access the website.We'll provide an update as soon as we can. If you need immediate help, please reach out to our Support team:https://zapier.com/app/get-help

We’ve finished sending out the Slack alerts that got stuck, and everything is caught up. Your Zaps with the Slack trigger should now run smoothly without delays. Thanks for bearing with us!

We are continuing to investigate this issue.

Users may have experienced delays with their Slack triggers, with slowdowns lasting approximately 10–20 minutes. This initially appeared to be resolved by 8th May 2025 - 17:34 UTC thanks to the efforts of our team. However, we are aware that the issue has resurfaced and are actively investigating it once again. We want to reassure users that no data loss has been observed. If you continue to encounter issues, please don’t hesitate to reach out to our support team at https://zapier.com/app/get-help. We sincerely apologize for the inconvenience and thank you for your continued patience.

Earlier today starting at 13:22 UTC ,users may have encountered slowdowns with their Slack triggers. The delays were approximately 10-20 minutes, which may have deferred some processes. Fortunately, this issue has now been resolved as of 17:34 UTC by our dedicated team. As a result, users should no longer experience any of the aforementioned delays. Importantly, there was no data loss observed during this incident. For any further issues, we kindly ask that you contact our support team at https://zapier.com/app/get-help We deeply appreciate your patience during this time and apologize for any inconvenience you might have experienced.

We are currently investigating an issue where some users are experiencing delays of 10-20 minutes or missing Slack triggers, causing some Zaps not to execute. We are working diligently to resolve this issue and restore normal function. We will keep you updated on our progress as we have more information. If you need further assistance, please reach out to our support team at: https://zapier.com/app/get-help. Many thanks for your patience!

We are currently investigating an issue where some users are experiencing delays of 10-20 minutes or missing Slack triggers, causing some Zaps not to execute. We are working diligently to resolve this issue and restore normal function. We will keep you updated on our progress as we have more information. If you need further assistance, please reach out to our support team at: https://zapier.com/app/get-help. Many thanks for your patience!

This is now resolved. You should be able to receive those emails from Zapier going forward. Also, we are currently going through and reprocessing emails that we not able to get send out during that issue, we can ensure you get that information. Thanks again for your patience, and if you are still running into issues with email deliverability, please reach out to Zapier Support: https://zapier.com/app/get-help

We have identified that this issue has affected more than just password reset emails, and is currently affecting multiple transactional email. This includes email address confirmation emails as well. In addition, we have also implemented a fix to get these emails starting to send back out, and are monitoring the results. Thanks again for your patience, and we'll provide any update here as soon as we can.

We've identified an issue where password reset emails are not being sent to users attempting to reset their passwords. Our team is currently working on a fix to resolve this problem as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience as we work to get this resolved. We will provide another update once the issue is fixed.

We've identified an issue where password reset emails are not being sent to users attempting to reset their passwords. Our team is currently working on a fix to resolve this problem as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience as we work to get this resolved. We will provide another update once the issue is fixed.

Today, May 1st, 2025 from 8:41AM CST to 11:44AM CST, some Zaps using Gmail triggers involving attachments encountered the following error: Error while hydrating data from Gmail: Cannot destructure property 'individualAttachments' of '(intermediate value)' as it is null. The error surfaced when we tried to process emails that did not include attachments. We are pleased to inform you that the issue has been resolved, and any triggered Zaps after 11:44AM CST will be processed normally. All affected customers will be notified via email with guidance and next steps. Thank you for your patience while we worked to resolve this! If you have any questions, please reach out at: zapier.com/get-help.

Users might have encountered the error “Cannot destructure property 'individualAttachments' of '(intermediate value)'” for Zaps using Gmail triggers involving attachments. The issue is resolved as our team has implemented a fix. Any Zaps triggering from now on (5pm UTC) should be processed correctly. Many thanks for your patience! We will continue to update this page as we gather more information.

We are currently investigating reports of issues with Gmail Triggers that include attachments, this behaviour was first identified at around 4:00pm UTC. An example trigger error is "Cannot destructure property 'individualAttachments' of '(intermediate value)' as it is null'. Our team is currently investigating this and we will update our status page when we have more information.

We are currently investigating reports of issues with Gmail Triggers that include attachments, this behaviour was first identified at around 4:00pm UTC.An example trigger error is "Cannot destructure property 'individualAttachments' of '(intermediate value)' as it is null'. Our team is currently investigating this and we will update our status page when we have more information.

The issue has been Resolved -- all Zaps and Zap drafts should now be able to publish without error or delay. Starting April 11th, some users reported errors when trying to publish Zap drafts. This error message would surface as: "Failed to publish new version. Zapier timed out while saving this version. Please try again." We've resolved the issues with publishing options and will further address version needs to avoid similar incidents in the future. If you run into any trouble accessing Zapier.com, please reach out to our Support Team: https://zapier.com/app/get-help We appreciate your patience during this incident and apologies for any inconvenience this might have caused.

We have identified an issue beginning on April 11, 2025, which is causing some users to be unable to publish their Zap drafts. This issue is unrelated to the configuration of the Zaps. The error message being displayed when attempting to publish a draft is: "Failed to publish new version. Zapier timed out while saving this version. Please try again." We appreciate your patience as we work towards a resolution. If you are encountering this issue and need further assistance, please don't hesitate to reach out to our support team at https://zapier.com/app/get-help. We will provide updates on this incident as soon as we have more information.

We have identified an issue beginning on April 11, 2025, which is causing some users to be unable to publish their Zap drafts. This issue is unrelated to the configuration of the Zaps. The error message being displayed when attempting to publish a draft is: "Failed to publish new version. Zapier timed out while saving this version. Please try again."We appreciate your patience as we work towards a resolution. If you are encountering this issue and need further assistance, please don't hesitate to reach out to our support team at https://zapier.com/app/get-help. We will provide updates on this incident as soon as we have more information.

Our team was able to find and resolve the issue and has since replayed all of the delayed webhooks. All Zaps should now be run! We appreciate your patience while we worked on this. If you have any questions or concerns, please reach out to Zapier Support: https://zapier.com/app/get-help.

We are currently investigating an issue with a delay with Zaps that use an Instant Trigger. The team is working on finding the root cause of the issue and appreciate your patience. We'll continue to post updates and information here as it becomes available. If you have any concerns or questions, please reach out to our Support team here: https://zapier.com/app/get-help.

We are currently investigating an issue with a delay with Zaps that use an Instant Trigger. The team is working on finding the root cause of the issue and appreciate your patience. We'll continue to post updates and information here as it becomes available. If you have any concerns or questions, please reach out to our Support team here: https://zapier.com/app/get-help.

We've confirmed that the errors have been fully resolved and all users should be able to login to their Zapier accounts again. If you continue to experience any login issues, you can reach out to our support here: https://zapier.com/app/get-help. Thank you for your patience and understanding as we worked to resolve this!

There's been a decrease in the 502 errors affecting the Zapier login. Users should be able to login again, but we'll keep monitoring to ensure it doesn’t resurface. We appreciate your patience and will continue to provide updates until this is fully resolved.

At approximately 11:30pm UTC our monitoring systems started to indicate that some attempts by users to login to Zapier may not be possible. We have seen reports of 502 Bad Gateway errors. Logins, signups, invitations, and password recovery functions are affected. We believe these errors are happening mainly for users logging in from around the Singapore region. Our team is currently investigating this and we will update our status page when we have more information.

At approximately 11:30pm UTC our monitoring systems started to indicate that some attempts by users to login to Zapier may not be possible. We have seen reports of 502 Bad Gateway errors. Logins, signups, invitations, and password recovery functions are affected.We believe these errors are happening for requests that go to the AWS region ap-southeast-1 (ie. around Singapore)Our team is currently investigating this and we will update our status page when we have more information.

Users may have experienced some difficulties with publishing photos on Instagram for Business via Zapier. We're pleased to inform you that this particular issue has now been fixed. Please note that posts from the past day have been replayed due to their time-sensitive nature. For any other posts, manual replays will be necessary. If you experience any additional issues or problems posting to Instagram Business via Zapier, do not hesitate to contact our Support Team at https://zapier.com/app/get-help. Thank you for your understanding and patience in this matter. We apologize for any inconvenience this may have caused.

We have implemented a fix for the issue affecting the Instagram for Business - Publish Photo action and are currently monitoring the results to ensure stability. Thank you for your patience while we worked to resolve this. We will continue to provide updates as necessary.

We are aware of a problem affecting the 'Publish Photo' action within 'Instagram for Business'. We are actively collaborating with the team at Meta, who handle Instagram's operations, to rectify the situation as quickly as possible. We are hopeful that a swift resolution can be found, and we appreciate your patience during this time. We understand the importance this feature has in your day-to-day operations, so please rest assured that its restoration is our absolute priority. Updates will be communicated via this status page, so kindly keep an eye out. We're deeply sorry for any inconvenience this may cause and we're grateful for your understanding.

We are aware of a problem affecting the 'Publish Photo' action within 'Instagram for Business'. We are actively collaborating with the team at Meta, who handle Instagram's operations, to rectify the situation as quickly as possible. We are hopeful that a swift resolution can be found, and we appreciate your patience during this time.We understand the importance this feature has in your day-to-day operations, so please rest assured that its restoration is our absolute priority. Updates will be communicated via this status page, so kindly keep an eye out. We're deeply sorry for any inconvenience this may cause and we're grateful for your understanding.

The issue regarding QuickBooks Online Integration Triggers being delayed has been resolved. Previously, some users experienced delays or missing webhooks due to a disruption in webhook delivery from QuickBooks. Your Zaps should now be functioning smoothly without any disruptions. If you encounter any further issues or need assistance, please contact our Support Team via our help page at https://zapier.com/app/get-help. Thank you for your patience and understanding.

We’re currently monitoring for the recurrence of an issue that was previously <a href="https://status.zapier.com/incidents/31gnlzkn41cm">resolved</a>. Earlier, we observed delays in webhooks from QuickBooks, and those delays appear to have returned. Intuit QuickBooks is actively working to resolve these delays. Our team is continuing to monitor the situation to ensure stability and will share updates as needed.

The issue affecting some users—where they were incorrectly receiving alerts stating, "You've surpassed your subscription's task limit"—has been resolved. If you continue to experience this issue or have any questions, please don’t hesitate to reach out to our Support Team: https://zapier.com/app/get-help. Thank you for your patience and understanding as we worked to resolve this!

We are currently monitoring a previously reported issue where some users were receiving email alerts informing them that they have exceeded their task limit. The specific notification stated, "You've surpassed your subscription's task limit." We have now released a fix to address this issue and will continue to keep a close watch on the situation to ensure the complete resolution of the issue. We kindly ask users who encounter further issues or have any questions to reach out to our Support Team at https://zapier.com/app/get-help. We appreciate your understanding and cooperation.

We are currently investigating an issue where users are receiving an error message indicating that they have surpassed their subscription's task limit, even though they have not. The specific error message being received is: "You've surpassed your subscription's task limit." The issue appears to be affecting the email notifications sent to users. Despite the error message, please note that the task number showing in your Zapier account remains accurate. At this time, we are not aware of any data loss related to this incident. We are currently working to resolve the issue and will update this status page as we have more information. If you experience any further issues, please do not hesitate to reach out to our support team: https://zapier.com/app/get-help

We are currently investigating an issue where users are receiving an error message indicating that they have surpassed their subscription's task limit, even though they have not. The specific error message being received is: "You've surpassed your subscription's task limit."The issue appears to be affecting the email notifications sent to users. Despite the error message, please note that the task number showing in your Zapier account remains accurate.At this time, we are not aware of any data loss related to this incident. We are currently working to resolve the issue and will update this status page as we have more information.If you experience any further issues, please do not hesitate to reach out to our support team: https://zapier.com/app/get-help

The issue we were experiencing with the Webhooks by Zapier integration is now resolved. During a period from 2025-04-14 04:36:43 UTC to 2025-04-15 16:31:00 UTC, the Webhooks by Zapier integration was returning an error "Not a legal HTTP header value" for a small percentage of runs. The root cause was identified and our team was able to deploy a fix to resolve this error. They also replayed any runs that returned this error to send them through successfully. If you have any questions or run into further issues feel free to reach out to our Support Team.

We've applied a fix for users experiencing this issue and have begun replaying Zap runs for the affected users. There is no data loss as a part of this incident. We'll continue to monitor this issue and give additional updates as soon as possible. If you have questions or are experiencing this issue, please contact Zapier Support via our website: https://zapier.com/app/get-help

We are currently seeing a small percentage of Webhooks by Zapier steps failing with an error "Not a legal HTTP header value." We are currently investigating the root cause of this issue and will provide additional information as soon as possible.

We are currently seeing a small percentage of Webhooks by Zapier steps failing with an error "Not a legal HTTP header value." We are currently investigating the root cause of this issue and will provide additional information as soon as possible.

The issue we were experiencing with our website is now resolved. Full access and functionality have been restored. During the brief period of inaccessibility on April 10 16:28 to 16:30 UTC, the full extent of functionality on Zapier.com was impacted. However, rest assured, no data was lost or compromised during this down time. The root cause was identified and promptly addressed. Further preventive measures have been implemented to reduce such incidents in the future. If you experience any issues while using Zapier.com, we encourage you to reach out to our Support Team via this link: https://zapier.com/app/get-help

Zapier.com was briefly unavailable from 16:28 to 16:30 UTC. During this short window, some users may have had trouble loading the site, and certain Zaps might not have triggered as expected. Everything is back up and running now, and we're keeping a close eye on things as we look into what caused the issue.

From 16:28 to 16:30 UTC, Zapier.com was briefly unavailable, and users may have experienced issues loading the site. During this time, data ingest failures also occurred, preventing some Zaps from triggering as expected. Service has since recovered, and the platform is currently operating normally. Our team is actively investigating the root cause to better understand what led to the disruption. We’ll share additional details as we learn more. If you have any questions in the meantime, please reach out to our Support team: https://zapier.com/help

From 16:28 to 16:30 UTC, Zapier.com was briefly unavailable, and users may have experienced issues loading the site. During this time, data ingest failures also occurred, preventing some Zaps from triggering as expected.Service has since recovered, and the platform is currently operating normally. Our team is actively investigating the root cause to better understand what led to the disruption. We’ll share additional details as we learn more.If you have any questions in the meantime, please reach out to our Support team:https://zapier.com/help

The issue regarding QuickBooks Online Integration Triggers failing has been resolved. Previously, some users experienced delays or missing webhooks due to a disruption in webhook delivery from QuickBooks. We’ve confirmed that the fix implemented by the QuickBooks team on April 8 successfully resolved the issue. The backlog of events that had accumulated prior to the fix has now been cleared, and Zap activity should be operating as expected. If you continue to experience issues with your QuickBooks Zaps, please reach out to our Support Team for assistance.

We have been informed by the QuickBooks team that a fix was applied on April 8, and they are observing improvements in the system's performance. However, there is a small backlog of events that were queued up prior to the fix, and the team is currently waiting for these to clear out. In response, we are actively monitoring performance to determine if the fix from QuickBooks Online (QBO) is effectively resolving the issues with webhook delivery. We appreciate your patience and will continue to provide updates as we progress toward a resolution.

We've identified an issue on April 2, 2025 with the QuickBooks Online Integration on Zapier. It appears that some triggers are failing which means a subset of users may see either a delay in receiving webhooks from QuickBooks or no webhook at all. We don't currently have a workaround for this, but we want to assure you that we're actively collaborating with the QuickBooks Online team to resolve this issue promptly. We recognize that this issue might disrupt your normal workflow, and we aim to keep you sufficiently updated about our progress. If you require further information or assistance concerning this development, kindly get in touch with our support team. Rest assured, we're doing everything we can to rectify this situation.

We've identified an issue on April 2, 2025 with the QuickBooks Online Integration on Zapier. It appears that some triggers are failing which means a subset of users may see either a delay in receiving webhooks from QuickBooks or no webhook at all. We don't currently have a workaround for this, but we want to assure you that we're actively collaborating with the QuickBooks Online team to resolve this issue promptly. We recognize that this issue might disrupt your normal workflow, and we aim to keep you sufficiently updated about our progress. If you require further information or assistance concerning this development, kindly get in touch with our support team. Rest assured, we're doing everything we can to rectify this situation.

The issue regarding user connection to Azure Active Directory via Zapier has been resolved. Users were previously experiencing difficulties in creating new connections or reconnecting existing ones, with an error message stating "Oh, foo. Zapier could not connect to your account. Perhaps you declined access? Or it could be a temporary issue." We are happy to confirm this issue has been rectified now. Users should be able to establish fresh connections or reconnect their previous ones without encountering the aforementioned error. We'd like to assure our users that all tasks impacted have been dealt with and replayed successfully, and no data was lost during this incident. If you experience any future issues or difficulties in connecting to Azure Active Directory via Zapier, we encourage you to contact our Support Team via our website: https://zapier.com/app/get-help

Authentications that were previously failing due to the incident have now been fully resolved and are functioning as expected. We're replaying all Zap runs impacted by the incident to ensure data consistency and integrity. We appreciate your patience and will continue to provide updates as we progress toward a resolution.

We've identified an issue that began on April 5th, 2025 at 6:38 PM UTC, affecting users attempting to connect or reconnect to Azure Active Directory via Zapier. Users are unable to create new connections or reconnect existing ones to Azure Active Directory. During connection attempts, users may encounter the following error: "Oh, foo. Zapier could not connect to your account. Perhaps you declined access? Or it could be a temporary issue." The root cause has been identified, and our team is actively working on implementing a fix. There is no indication of any data loss related to this incident. We appreciate your patience and will continue to provide updates as we progress toward a resolution.

We're aware of an issue that affected some users who didn't receive error alerts, usage notifications, and password reset emails from us. This was due to an influx of errors with our email service provider. Our engineering team identified the root cause and applied a fix. Emails should be delivered consistently again now. If emails continue to not be delivered, please reach out to our Support Team here: https://zapier.com/help

We would like to provide an update on the recent incident that impacted user notifications on Zapier. This incident began on Friday, March 28th and was resolved on Monday, March 31st at 17:55 UTC. The issue specifically affected some error alerts, usage notifications, and password reset emails, which were not being delivered as expected. Our team worked diligently with our email providers to rectify the sending issues. As a result, any error messages and system notifications going forward should notify you without delay. Concerning password resets, users who have reset their passwords after the fix or at any time now should face no difficulties. We acknowledge that some users may have missed important error messages and system notifications due to this incident. Our team is now working to resend these notices. We want to assure you that there was no data loss during this incident. Your Zaps continued to run and process as expected. We're now in the monitoring phase to ensure our fix is holding up and everything continues to run smoothly. Please feel free to reach out to our Support Team if you have any additional questions: https://zapier.com/app/get-help. Kindly check back this status page for further updates. Your patience and understanding during this period is highly appreciated.

We are currently investigating an issue affecting user notifications on Zapier, specifically error alerts, usage notifications, and password reset emails that are not being delivered. This issue started on Friday, March 28th. The investigation is ongoing and our team is working diligently to resolve the issue. While we do not currently have an estimated resolution time, we will continue to update this space with any new information as it becomes available. Should you require assistance or have any questions or concerns, please don't hesitate to contact our Support team at: https://zapier.com/app/get-help.

We've identified an issue that began on April 5th, 2025 at 6:38 PM UTC, affecting users attempting to connect or reconnect to Azure Active Directory via Zapier.Users are unable to create new connections or reconnect existing ones to Azure Active Directory. During connection attempts, users may encounter the following error:"Oh, foo. Zapier could not connect to your account. Perhaps you declined access? Or it could be a temporary issue."The root cause has been identified, and our team is actively working on implementing a fix. There is no indication of any data loss related to this incident.We appreciate your patience and will continue to provide updates as we progress toward a resolution.

Our team has resolved the issue encountered earlier which caused some delays and errors in task processing, as well as slow loading times on our logged-in homepage. Thank you for your patience and understanding while our team addressed these issues!

We have identified the root cause of the delays and errors in task processing, as well as the slow loading times on our logged-in homepage. Our team has temporarily scaled up the system resources, which has improved performance.

The problems started at 10:31 PST today. They are affecting: Task Processing: Some tasks are delayed or not completing correctly, especially in areas of our service that handle a lot of data at once. Homepage Loading: It’s taking longer than usual for the main parts of our website to appear after you log in.

Our team has resolved the issue encountered earlier which caused some delays and errors in task processing, as well as slow loading times on our logged-in homepage. Thank you for your patience and understanding while our team addressed these issues!

We have identified the root cause of the delays and errors in task processing, as well as the slow loading times on our logged-in homepage. Our team has temporarily scaled up the system resources, which has improved performance.

The problems started at 10:31 PST today. They are affecting:Task Processing: Some tasks are delayed or not completing correctly, especially in areas of our service that handle a lot of data at once.Homepage Loading: It’s taking longer than usual for the main parts of our website to appear after you log in.

We are currently investigating an issue affecting user notifications on Zapier, specifically error alerts, usage notifications, and password reset emails that are not being delivered. This issue started on Friday, March 28th. The investigation is ongoing and our team is working diligently to resolve the issue. While we do not currently have an estimated resolution time, we will continue to update this space with any new information as it becomes available.Should you require assistance or have any questions or concerns, please don't hesitate to contact our Support team at: https://zapier.com/app/get-help.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be undergoing scheduled maintenance at this time. During this window, there will be roughly 25 seconds of planned downtime for Audit Logs.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be undergoing scheduled maintenance during this time.

The earlier incident impacting hooks has been resolved as of 5:12 PM UTC. The issue started at 4:31 PM UTC and resulted in a delay of up to 10 seconds. We sincerely thank you for your patience during this period. Our team has now confirmed that hook processing speeds are back to normal. We are currently investigating possible data loss, and further information will be provided directly to any impacted customers. Should you experience any further problems, please reach out to our support team here: https://zapier.com/app/get-help

We are currently investigating an issue affecting Zapier, which is causing a delay of about 10 seconds in webhook processing. This incident began at 4:31 PM UTC and is ongoing. We appreciate your understanding and patience while we work towards resolving the issue. We will provide updates as and when we have more information. Please follow this page for regular updates. Thank you.

The earlier incident impacting hooks has been resolved as of 5:12 PM UTC.The issue started at 4:31 PM UTC and resulted in a delay of up to 10 seconds. We sincerely thank you for your patience during this period.Our team has now confirmed that hook processing speeds are back to normal. We are currently investigating possible data loss, and further information will be provided directly to any impacted customers.Should you experience any further problems, please reach out to our support team here: https://zapier.com/app/get-help

We are currently investigating an issue affecting Zapier, which is causing a delay of about 10 seconds in webhook processing. This incident began at 4:31 PM UTC and is ongoing. We appreciate your understanding and patience while we work towards resolving the issue. We will provide updates as and when we have more information.Please follow this page for regular updates. Thank you.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be undergoing some maintenance during this time. This maintenance will log out some users from Zapier. Anyone logged out can log back in normally.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be undergoing scheduled maintenance during this time.

This issue with PayPal triggers not triggering consistently has been resolve. Missing Zap Runs since March 8th 13:43 UTC have been recovered and replayed. For any questions about this incident, please reach out to our Support team: https://zapier.com/help

We have identified an issue that began on March 5th at 12:00 UTC, where PayPal triggers on Zapier were intermittently not triggering as expected. Our team pushed a fix for this issue on March 13th at 1:45 UTC. Missing hooks from March 5th 12:00 UTC to March 8th 13:43 UTC weren't able to be recovered. If you had any data that didn't transfer during this time frame, you will need to manually send that data to the destination app. Our team is working to recover any missed trigger events that occurred from March 8th 13:43 UTC to March 13th 1:45 UTC. We appreciate your understanding during this time. If further assistance is needed, please reach out to our Support Team.

This issue has been resolved. Agent triggers are working as expected. If you're still experiencing failed trigger events, please log out and then back into your account. For any questions about this incident, please reach out to our Support team: https://zapier.com/help

All Agent triggers should now be working. If you're still experiencing failed trigger events, please log out and then back into your account. We're still exploring the possibility of replaying any missed events that occurred during this time frame.

As of March 6, 2025, at 10:00 AM UTC, users who haven’t logged into their Zapier Agents account in the past 7 days will experience failed trigger events. To resolve this issue, please log out and then log back into your Agents account. We are actively working on a permanent solution and are also exploring the possibility of replaying any missed events.

This issue has been Resolved- Zapier Interface pages are fully accessible. On March 7th an issue arose where Interfaces pages were having trouble loading and were returning 500 errors. A fix was implemented and Interfaces are working as expected again. If you have further questions, please reach out to our Support Team here: https://zapier.com/app/get-help

We've implemented a fix to address the issue that was causing this. The fix has now mitigated this impact, and Interfaces should be working as expected. If the issues persist, login into zapier.com should help mitigate those errors. We'll continue monitoring and update this StatusPage once we're confident the fix has fully resolved the issue. If you have further questions, please reach out to our Support Team here: https://zapier.com/app/get-help

We're currently experiencing an issue where published Interfaces can't be accessed. We're currently investigating this issue and working on how to mitigate the impacts. We appreciate your patience while we resolve the issue. Please reach out to our Support Team if you need anything: https://zapier.com/app/get-help

We have resolved the issue with API tokens when using the AI by Zapier app. If you continue running into errors, please let our support team know: https://zapier.com/app/get-help

We are currently investigating an issue with our AI by Zapier integration. Users have been experiencing 500 errors - the specific message reads "Unexpected error fetching AI response, status: 500". At this point, we don't have a known workaround and we are diligently investigating the issue.

There was a recent incident where our users were facing issues with stale authentication for several Microsoft applications including Microsoft Outlook, Microsoft To Do, Microsoft Office 365, Microsoft Exchange, and OneDrive on our platform. We're happy to report that this incident has been resolved. Should you still encounter issues with your Microsoft applications, please manually reconnecting the affected account(s). You can do so by following the instructions outlined in our Help Center: https://help.zapier.com/hc/en-us/articles/8496290788109-Manage-your-app-connections#01JH3AK29AAFDNP7AS4PQ1NNM6. For affected action steps, you can replay your Zap runs once you have reconnected your account. For Zaps using triggers from these affected apps, Zaps would not have received events to trigger the Zap due to the stale authentication, so Zap runs would not have been processed during this time. We recommend reviewing your workflows to see if there were missing Zap runs and manually enter missing data as needed. If you have further issues or require additional assistance, feel free to reach out to our support team at https://zapier.com/app/get-help. We appreciate your understanding during this incident and apologize for any inconvenience it may have caused.

Our engineering team has reconnected stale authentications for the following Microsoft apps, and they should now be working as expected: - Microsoft Outlook - Microsoft To Do - Microsoft Office 365 - Microsoft Exchange - OneDrive If you're still experiencing issues, please try manually reconnecting your account by following these steps: https://help.zapier.com/hc/en-us/articles/8496290788109-Manage-your-app-connections#01JH3AK29AAFDNP7AS4PQ1NNM6 If you continue to have trouble after reconnecting manually, please let our support team know at: https://zapier.com/app/get-help.

We are currently investigating an issue where some Microsoft Outlook accounts disconnected due to a global Outlook outage on March 1st, 2025. Our Engineering team is actively investigating this incident, and we will keep updating this page as we learn more. If you have any questions, our support team can be contacted at: https://zapier.com/app/get-help.

There was an incident recently where our users experienced connection errors and error messages while using our Google Ads integrations. The errors were disrupting the successful execution of Zap Runs. We want to inform you that the issue has been resolved. With the exception of users utilizing our '(Legacy) New Lead Form' trigger, If you've been experiencing issues with your zap runs, these should now connect and function without any error. For users utilizing the '(Legacy) New Lead Form Entry' trigger, you can replay any errored Zap runs from this trigger by 1) ensuring your Google Ads connection is working, and 2) replaying errored tasks in Zap History If any user still experiences issues, we encourage them to reach out to our Support Team here: https://zapier.com/help

Due to an ongoing issue reported by Google, Google Ads integrations are showing error messages instead of successfully completing Zap Runs. You can find out more on Google's Status Page: https://ads.google.com/status/publisher/incidents/3UvgRRh1d4sS3FoEEDCm Our team is actively monitoring the situation for changes. If you have any questions, please reach out to our Support team: https://zapier.com/help

Issues regarding Email Parser and Email by Zapier are now resolved

Around 4:30AM UTC, an incident was reported causing issues with Email by Zapier and Zapier Email Parser triggers. This meant that emails being forwarded to these services did not trigger related Zaps as expected. We are pleased to inform you that a fix was found and implemented at 6:25AM UTC and we have observed that new emails being forwarded to both Email by Zapier and Zapier Email Parser are now correctly triggering the associated Zaps. For the emails that weren't processed during the incident period, our team is currently looking into the possibility of replaying them automatically. Our team will continue to monitor the situation closely to ensure all services are functioning as they should. If you have any further questions, feel free to contact our Support Team. https://zapier.com/app/get-help

Our team is aware of and currently investigating an issue where users are intermittently unable to receive emails to their Email Parser by Zapier and Email by Zapier mailboxes. This is resulting in Zaps not triggering. We'll provide an update as soon as we have more information. If you have any questions, please reach out to our support team: https://zapier.com/he

As of February 28, 03:28 UTC, Slack has resolved the issue affecting event delivery, and new events are now processing as expected. However, Slack has confirmed that missed events from the outage between February 27, 02:15 UTC and February 28, 03:28 UTC will not be replayed. This means any Zap runs triggered by Slack events during this period were lost and cannot be recovered. For more details, refer to Slack’s official status update: https://slack-status.com/2025-02/d41e4bfd1ccae26a We apologize for the disruption and appreciate your patience. If you need assistance adjusting your Zaps, please reach out to our support team. https://zapier.com/help

We're seeing some reports of reduced delays in processing incoming webhooks from Slack. We will continue to monitor the situation and provide updates here.

We identified that the Slack incident caused missed triggers between February 26th 18:00 UTC and February 27th 6:30 UTC. 
 While we’re now receiving webhooks from Slack again, we’re still seeing some delays in processing them. We’re communicating with the Slack team to address these issues and understand if the missed triggers can be recovered. We will continue to monitor and update this StatusPage within then next 24 hours. If you have further questions, please reach out to our Support Team here: https://zapier.com/app/get-help

Slack is undergoing an incident right now (https://slack-status.com/2025-02/1b757d1d0f444c34) which is resulting in delayed Zap trigger processing for Zaps powered by Slack triggers.

Slack is undergoing an incident right now (https://slack-status.com/2025-02/1b757d1d0f444c34) which is resulting in delayed Zap trigger processing for Zaps powered by Slack triggers.

We've successfully rectified an issue which previously prevented users from accessing and using the Zap Editor. Users were faced with a 'HTTP ERROR 500' message. We're pleased to let you know that you can now access and use the Zap Editor without any errors. Please, do not hesitate to reach out to our Support Team via https://zapier.com/app/get-help if you encounter any further difficulties while accessing Zapier.com.

Our team has implemented a fix and we're monitoring the issue for any ongoing changes. Users should be able to access the Zap Editor once again. If you find you're running into a 500 error, please try a hard refresh of your browser page. We'll provide an update once this has been resolved. If you have any questions, please reach out to our support team: https://zapier.com/help

Our team is currently investigating an issue where users are unable to access the Zap Editor to create or edit new Zaps. When attempting to access the Editor, users are seeing a 500 error. Users can still disable and enable Zaps from the Zap Dashboard. We'll provide an update as soon as we have more information. If you have any questions, please reach out to our support team: https://zapier.com/help

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.

Our engineering team has resolved the issue with reset password links not functioning properly if the email was scanned by Microsoft Defender. The reset password link will now remain valid as long as the request to reset your password is less than 24 hours old when the email is delivered.

Our engineering team has resolved the issue with reset password links not functioning properly. The reset password link will now remain valid as long as the request to reset your password is less than 24 hours old when the email is delivered. However, we're still investigating the issue where Microsoft Defender is blocking emails from security@mail.zapier.com. If you are affected, please check your Microsoft Defender admin settings to ensure that security@mail.zapier.com is marked as a safe sender. In the meantime, if you are not receiving the password reset email, please ask your email admin to try the following steps: 1. Log into the Admin Office account: https://security.microsoft.com/quarantine 2. Click the menu on the left > Email & Collaboration > Review 3. Select the Zapier password reset email “Under Review” and press “Release Email” 4. This should return the reset email back to your inbox 5. If the reset link is expired, please try sending another email: https://zapier.com/app/login/forgot 6. You may also need to click "Trust Sender" and "Show Blocked Content" to get the link to work We appreciate your patience as we continue working on this. Please reach out to our Support team if you need further assistance: https://zapier.com/app/get-help

We have identified the issue causing Microsoft Defender to block emails from security@mail.zapier.com. In some cases, even when the email is delivered, links within the email may not function properly. Some customers have been able to log in to their accounts using Google, Facebook, or Microsoft login options as a workaround. <img src="https://cdn.zappy.app/3e84c70ae5aabb91bcaad2f28d992e50.png">

We are currently investigating an issue where Microsoft Defender is blocking emails from security@mail.zapier.com. In some cases, even when the email is delivered, links within the email may not function properly. If you are experiencing this issue, please check your Microsoft Defender admin settings and ensure that security@mail.zapier.com is marked as a safe sender or allowed. Additionally, verify that the emails are not being quarantined or filtered. If you do not have access to these settings, we recommend reaching out to your IT department to review and update them accordingly. For guidance on handling false positives in Microsoft Defender, please refer to the following guide: https://learn.microsoft.com/en-us/defender-office-365/step-by-step-guides/how-to-handle-false-positives-in-microsoft-defender-for-office-365 We appreciate your patience while we resolve the issue. Please reach out to our Support Team if you need anything: https://zapier.com/app/get-help

Our team has fixed the throttling issue and replayed any effected runs. All Static IP Zaps should be back to fully functional now.

We've identified an issue with apps using Static IP addresses. During affected times this may have resulted in throttling or errors of Zap Runs using affected apps. The incident began at 15:15 and ended at 15:35 UTC. As of now, Zap Runs should be functioning as expected. If you encounter any issues or errors related to Zap Runs during the incident, they can be replayed. No data loss is anticipated from this incident. For any further queries or assistance, kindly reach out to our Support Team: https://zapier.com/app/get-help

This incident is resolved. If you continue to have issues, contact our Support team: https://zapier.com/app/get-help

We're investigating an issue where approval popups appear for Enterprise users when toggling Zaps on/off from the My Zaps page although the account has opted out of this feature. You can still toggle Zaps via the Zap Editor. Our team is working on a fix, and we'll post updates here. For further assistance, contact our Support team: https://zapier.com/app/get-help

This incident has been resolved.

We are monitoring an issue where some accounts are being prompted for approval while in the Zaps list page when trying to turn Zaps on/off. Workaround: You can still turn on/off your Zaps while in the Zap editor instead of on the Zaps list page.

This incident has been resolved. Our team implemented a fix and users should no longer see the 500 Error messages across Zapier.com. If you have further questions or need assistance, please reach out to our support team at https://zapier.com/app/get-help.

Our team has been investigating reports of users that use Chargebee payments set up for their account billing who are running into 500 errors across Zapier.com. This primarily impacts users that pay via invoice. We have identified the cause of the error and taken steps with Chargebee's team to reduce the errors. We are currently monitoring our logs to ensure this clears up the issue. Thank you again for your patience while we've worked on this. We will provide additional updates as soon as possible.

We are investigating reports of users that have a Chargebee payment set up for their account billing who are running into 500 errors across Zapier.com. This primarily impacts users that pay via invoice. Thank you for your patience while we investigate this and we will provide updates as soon as we have additional information

We are investigating reports of users that have a Chargebee payment set up on their account are running into 500 errors across Zapier.com. Thank you for your patience while we investigate this and we will provide updates as soon as we have additional information

We have determined that this issue is due to a bug with Atlassian’s platform, and they are actively working on a resolution. While this continues to impact some functionality, we no longer classify it as an active incident on our end. For further updates, please refer to Atlassian's Developer Community. https://community.developer.atlassian.com/t/post-rest-api-3-search-jql-does-not-respect-maxresults-param/88287 Thank you for your patience. If you experience any additional issues, please reach out to our support team.

We are monitoring an issue with Jira Software Cloud that's causing various issues in Zaps using the Jira Software Cloud integration, including but not limited to delayed triggers, Zaps missing samples in the Zap editor, and timeouts in actions. We are working swiftly to find a solution and hope to have an update as soon as possible.

This incident has been resolved. Our team implemented a fix and we have successfully replayed any missed hooks from the past 5 days, so your zaps should now function as expected. If you have further questions or need assistance, please reach out to our support team at https://zapier.com/app/get-help.

A fix has been implemented for the LinkedIn app integration issue. We have successfully replayed missed hooks from the past 5 days and are currently monitoring the results.

We’ve identified an issue in our LinkedIn integration affecting Zaps that rely on the New Lead Gen Form Response trigger. Our engineering team is actively working on a fix. If you have further questions, please contact our Support Team here: https://zapier.com/app/get-help

We are investigating reports that some Zaps are triggering intermittently for the LinkedIn app integration.

This incident has been resolved. Trigger events for the Slack app were taking longer than normal, delaying Zap runs. The cause has been identified and fixed. No more delays should be experienced. If you have additional questions or need assistance, please don’t hesitate to reach out to our support team at https://zapier.com/app/get-help.

We're currently seeing that trigger events for the Slack app are taking longer than normal. We are investigating the cause of this slowdown.

On January 15, we experienced a brief issue from 02:00 pm UTC to 02:30 pm UTC, where users experienced an error message stating "Unable to access Zap", which is now resolved. This issue affected the ability to access or create Zaps from various platforms including email links, templates, shared zaps or Zap Guesser. Normal functionality in the Zap Editor was also affected. It's important to note that no data loss occurred during this incident, and all operations relating to Zap Runs and Tasks continued to function as expected. We have identified the issue was caused by our sessions database reaching its storage capacity limits which interfered with consistent access to [Zapier.com](http://zapier.com/) pages. To mitigate such incidents in the future, we will be making necessary adjustments and closely monitoring our database storage capacity. Should you encounter any further issues while accessing Zapier.com, please do not hesitate to contact our Support Team through https://zapier.com/app/get-help. Your continued patience and understanding throughout this incident are greatly appreciated. We apologize for any inconvenience this may have caused.

This incident has been resolved. Our team implemented a fix and delays Approval Request delays are back fo normal as of January 14th at 1:00 AM UTC. The internal systems are back to processing events as they come in. If you have additional questions or need assistance, please don’t hesitate to reach out to our support team at https://zapier.com/app/get-help.

We are currently investigating an issue that began around 02:00 UTC on Saturday, Jan 11, 2025, affecting customers on Enterprise plans. Approval requests may remain in a pending state in the UI, even after the approval action (e.g., publishing a Zap) has been completed by the account owner or super admin. Although the request shows as pending in the UI, the approval action is successfully processed. The delay is related to the UI updating the request’s status and does not affect the underlying action. Our team is actively working on resolving this issue and will provide updates here as soon as we have more information. For more details on how approvals work, please visit this article: https://help.zapier.com/hc/en-us/articles/21705940108941-Enable-publishing-restrictions-in-your-Enterprise-account If you have additional questions or need assistance, please don’t hesitate to reach out to our support team at https://zapier.com/app/get-help. Thank you for your patience as we work to resolve this issue.

This incident has been resolved. On Dec 16th at 4:27 PM UTC, Stripe connections began failing, and attempts to reconnect returned the following error: 'Invalid auth connection' Our team implemented a fix at 5:30 PM UTC on the same day. Due to these authentication errors, some Zaps using a Stripe trigger were turned off. As of 9:30 PM UTC on Dec 16th, our team unpaused these Zaps. During the downtime, we continued to receive hooks for paused Zaps, and any failed Zap runs were replayed by our team as of Dec 17th at 6:01 PM UTC. No data was lost. We appreciate your patience during this incident and sincerely apologize for any inconvenience caused. If you have any further questions, please don’t hesitate to reach out to our support team here: https://zapier.com/app/get-help.

We are currently looking into an issue where users experienced errors when trying to establish a connection with Stripe. The specific error message was 'Invalid auth connection.' We are pleased to report that we have implemented a fix and users should now be able to reconnect/enable any Zaps using Stripe without encountering the earlier problem. If any further issues arise or you do have questions, please do not hesitate to contact our dedicated Support Team, which can be reached via this link: https://zapier.com/app/get-help We do apologize for any inconvenience that this may have caused and appreciate your understanding as we worked to resolve the issue. We will continue to monitor the situation closely.

We’re currently investigating an issue where Stripe auths are expiring, and attempts to reconnect return the following error: 'Invalid auth connection.' We’ll update this page with more information as it becomes available. If you have any questions, please contact our support team at https://zapier.com/app/get-help.

Between 08:45 to 14:25 UTC, ActiveCampaign had an incident involving a high database load which in turn caused a delay in processing webhooks on Zapier's end. The ActiveCampaign team has since resolved the issue and our team has collaborated with them to process the delayed hooks properly. If you are still experiencing a delay in your ActiveCampaign Zaps, please don't hesitate to reach out to our Support team at https://help.zapier.com/.

We are investigating an issue that started today at around 08:30 UTC and involves the ActiveCampaign webhook triggers on Zapier which are failing to deliver the expected data. This is due to an outage in the ActiveCampaign API that we rely on for this service. Users may notice a delay in the triggering of their Zaps that use ActiveCampaign webhook triggers. There is no data loss associated with this incident. We reassure you that all data will be available once normal service has been resumed. No workaround is available at this moment. We will notify you as soon as the situation is resolved and normal service has been reinstated. In the meanwhile, our team is actively investigating this issue. Users who need assistance can contact our Support Team: https://zapier.com/app/get-help. We appreciate your understanding and patience as we work to resolve this disruption.

The issue affecting the loading of Logs ( Beta ) feature in Zap history has been resolved. The incident occurred at approximately 16:00 UTC, and was successfully fixed by 21:30 UTC. Our team promptly identified and solved the problem, ensuring that all Zap History logs are now displaying correctly. If you encounter any further issues, please don't hesitate to contact our Support Team. We thank you for your understanding and patience during this time.

Our team has now implemented a fix for our log reporting tools to clear up this Logs ( Beta ) readout. Kindly be assured that your Zaps and runs have not been affected, this problem was only with the visuals. We want to assure you that no data has been lost during this incident. While there was a Contact support error message popping up earlier, this has now been addressed, and the issue is resolving. However, there might be an occurrence of one-off errors, but these should be rare. We're keeping a close eye on the situation and continue to monitor the status. If you do encounter any further issues, please do not hesitate to contact our Support Team here: https://zapier.com/app/get-help

We have identified an issue affecting the Logs ( Beta ) feature in Zap history. As a result of this problem, logs may not be displaying as expected and users might encounter an error message or an unresponsive blank panel when trying to access these logs. The issue we have identified is related to our log reporting tools and how this displays in the history. We want to reassure you that there is no data loss associated with this incident. All Zaps and operations are functioning as normal. This issue is primarily affecting the viewing of logs in the history dashboard. We are actively working on resolving the matter as quickly as possible. However, the issue might still occur sporadically as we enhance the log reporting function. If you have further questions, please reach out to our Support Team here: https://zapier.com/app/get-help

As of 4:04 PM UTC, you may be seeing issues when loading the Logs ( Beta ) feature in your runs within Zap History. Our Team is currently investigating this, and we appreciate your patience as we work to resolve this issue. If you need further assistance, please do not hesitate to reach out to our Support Team: https://zapier.com/app/get-help.