This post was inspired by a message that Sergi Dominquez sent me on Twitter. It turns out, that when a request from Actionable Message in Outlook is sent to a server, Outlook waits only a specific amount of time for the response.
In Adaptive Cards there are multiple ways to show and hide content depending on other content or conditions, or even user interaction. But despite that most of them is available since the version 1.2 (so quite early) it requires a bit of knowledge how to actually implement them.
I am working with Power Automate Desktop for more than a year now. Over that time I faced a lot of weird errors that were occurring somewhere between cloud flows I used to trigger RPA and the bots themselves. Let me help you understand where are they coming from and how to resolve them (or create workaround).
Images always enricher Adaptive Cards designs. However in Microsoft Teams max. message payload is just 25KB and that includes also the size of card’s JSON. Therefore it is very often not possible to display even the smallest image inline. What other options we have?
When writing my previous post on working with Tasks in Power Automate I realized existence of a column name Flow Notification URI inside of Flow Approval table, which I so far really underestimated. Let me show you how powerful it is!
After I have successfully published and got certified with my first connector in the Independent Publisher connectors program (myStrom connector), I decided to share my journey and experiences with you, so that you can as well share your work with the whole world!
This is a re-post of the summary we wrote as a team after participating in hackathon during the South Coast Summit this year. The event was epic. The hackathon even more. Enjoy! The app and more details about our solution can be found here: https://github.com/LuiseFreese/HackSouthCoastSummit/.
I was seeing this kind of error in Nintex for Office 365 workflows for some time, but actually never had enough determination to check what is the root cause. However when customer started asking, I started digging.