You’re offline. This is a read only version of the page.
I have finally reached my boiling point with Flow. I used to be a huge proponent, but I can't do it anymore. It is extraordinarily unreliable, which, really, is on-par for Microsoft. So it's not surprising. How do they think that this tool could ever be implemented in a corporate/business setting is beyond me. It’s laughable to be honest. Flows just break all of a sudden. Unhelpful error messages (seriously, if I have to see that stupid ‘Cannot read properties of “push”...’ or whatever it says one more time...) The error messages are absolutely useless. They don’t help whatsoever. When you fix something, something else breaks. One thing after another. All the ‘transient errors’— sure, they fix themselves eventually and that’s great for going forward, but it doesn’t help with all the failed runs and whatever tasks Flow was supposed to handle. In typical MS fashion when trying to report bugs, they just ask you for more and more information and ask you to do this and do that; go here, look for this, take a screenshot, clear the cache, etc until you finally just give up. No one has time for that! We’re busy working around other bugs in MS products for crying out loud!
I don’t know what changes were made recently, but it’s all but killed Flow. It’s a dumpster fire that MS can’t seem to get a handle on. Read through some posts on here. Count the number of solutions that utilize a workaround. It’s abysmal. Consumers deserve better than this. Maybe put that shiny, good-looking, but ultimately broken 7000th new feature on the back burner and fix some of the numerous bugs. Has anyone at MS ever thought of taking this approach? This is NOT enterprise software. It’s broken. Period. Like everything else from MS. Oh, but now you can connect all the broken apps together! Sweet! Lot of good that does.
Share
Report
All responses (
Answers (
589
