Note: This post was is a reply to this post
FEEDBACK: If there is a known issue with a Zap app, then it’d be great if this was somehow indicated on the Zap app profile help page, perhaps as a new article.
Having known issues not publicly accessible for reference ultimately is a waste of time for everyone involved.
Being able to know when an issue was reported or started and when it was resolved or if it’s still open as a history log would be idea, especially for troubleshooting, a la the Zapier Status page incident history: https://status.zapier.com/#incidents-list
Thanks for this feedback, Troy - it’s great to hear from you!
First of all, I absolutely hear you on this, there are times when knowing something is an issue will help users to troubleshoot and move quicker. Let me share a little of where we’re coming from and what we are doing along these lines.
We don’t share all known issues because some bugs can be tricky to diagnose, especially without seeing the logs of a Zap. Sometimes, two issues can look the same on the surface, but be caused by two different factors and we don’t want to confuse users with that kind of information.
That said, we do want to help users to better understand some of the trickier apps, their quirks and common issues. The Community team is currently working with the Help docs, Users education and Support teams at Zapier to identify common issues with apps so we can create articles to publish on the Community. We hope that this will help users to troubleshoot their Zaps and better understand different app integrations.
If you have any suggestions for apps that you think we should start with, please let us know!