Identified - We've identified an issue with hitting limits in updating our history database leading to increased delay for tasks to show up on the website - tasks themselves are not effected.
May 08, 2024 - 15:37 PDT
Investigating - We are currently investigating an issue with our Zap history feature. As of 7:10PM UTC, new Zap Runs are being processed as usual, but they are not appearing in the Zap history. To clarify the user impact, all tasks and automations are still functioning as expected; the only difference is that new actions are not being recorded in your Zap history log. We are actively working to identify and address the cause of this issue. Your existing operations should not be affected during this time and you can continue to use Zapier as normal for your tasks and workflow automations. Thank you for your patience as we work on resolving this. If you need further assistance, feel free to reach out to our Support Team at https://zapier.com/app/get-help.
May 08, 2024 - 13:11 PDT
Resolved -
We have confirmed that the incident has been fully resolved as of 21:30 UTC.
Zap Runs history is expected to be fully available with no loss of data. All Zaps and Runs are confirmed to have played during the time of the incident.
Monitoring -
We're currently monitoring an incident that occurred between 6:10PM and 7:22PM UTC. As of now, new Zap runs should be visible in the Zap history page. However, we are aware that there may be some missing Zap runs that processed during this timeframe that are still not showing up. Our team is still investigating this issue to ensure everything is functioning as it should be. Please be informed that your Zaps continue to process without any disruptions. We're committed to providing another update as soon as we have more information. If you need assistance or further information, feel free to contact our Support Team here: https://zapier.com/app/get-help. We appreciate your patience and understanding during this time, and we are dedicated to resolving this issue swiftly.
May 2, 12:10 PDT
Investigating -
We are currently investigating an issue with our Zap history feature. As of 6:10PM UTC, new Zap Runs are being processed as usual, but they are not appearing in the Zap history. To clarify the user impact, all tasks and automations are still functioning as expected; the only difference is that new actions are not being recorded in your Zap history log. We are actively working to identify and address the cause of this issue. Your existing operations should not be affected during this time and you can continue to use Zapier as normal for your tasks and workflow automations. Thank you for your patience as we work on resolving this. If you need further assistance, feel free to reach out to our Support Team at https://zapier.com/app/get-help.
May 2, 11:00 PDT
Resolved -
Summary - On Thursday, April 25th, Zapier AI Actions experienced an issue that caused custom GPTs to error out with the message ""Exposed.create_execution() missing 1 required positional argument: 'user'". "
Resolution - Our investigation revealed that the error, "Exposed.create_execution() missing 1 required positional argument: 'user'", was caused by a configuration issue within our system. Our development team swiftly addressed this issue and implemented a fix to ensure the proper functioning of Zapier AI actions in custom GPTs.
System Status - All affected systems are now operating correctly, and users should no longer encounter any errors when utilizing Zapier AI actions within custom GPTs. We have conducted thorough checks to ensure there is no data loss resulting from this incident.
Contact Support - If you experience any further issues or have any questions, please do not hesitate to contact our support team. They are available to assist you promptly and ensure a smooth experience with Zapier.
We appreciate your understanding and cooperation as we worked to resolve this matter. Your satisfaction is our top priority, and we remain committed to providing you with the best possible service.
Apr 25, 08:38 PDT
Monitoring -
The team has shipped a fix for this issue and all your Zaps should now work as expected.