LowCodeStacks™
Sign in

Guides · 119

What are you trying to do?

Fix a problem

12The error or symptom in front of you, and the fix.

Choose a tool

2Decide before you build.
  • Power Automate

    Cloud flow, agent flow or desktop flow? Which one to build

    Three kinds of flow, three ways to pay. What each is for, how it's licensed or billed, what it can't do, and a quick way to pick: connectors and APIs, an agent's tools, or clicking through an app that has no API.

  • Power Automate

    Cloud flows or Azure Logic Apps?

    Power Automate and Azure Logic Apps share a designer and many connectors, but they're built for different owners, scales and controls. How to choose, and when to move a flow across.

Design patterns

4Structures that hold up as things grow.
  • Power Automate

    Child flows that fail well: inputs, results, errors and connections

    Child flow error handling that works: split a big flow without losing track of failures. Set up the child so it always reports back, let the parent decide what to do, avoid the 'child workflows only support embedded connections' error, and license it correctly.

  • Power Automate

    Reminder emails for items due soon: a daily flow that gets dates right

    Send a reminder a set number of days before a SharePoint due date. A daily scheduled flow that works in your time zone, filters the list efficiently, avoids double-sending, and can send one digest per person instead of a flood of emails.

  • Power Automate

    Try, catch and finally: error handling with scopes

    In Power Automate, a failed action just stops the flow by default, and the owner may never hear about it. The try-catch-finally pattern with scopes makes every failure visible, logged and handled.

  • Power Automate

    UI elements that survive changes: robust selectors for desktop flows

    UI element not found in a Power Automate desktop flow after an app update, a new window title or a different screen? Make selectors that keep working: find what changes, remove the dynamic parts, add fallback selectors, wait for the screen, and repair quickly when it does break.

Measure

1Know whether it's working.

Quick reference

5Error codes, limits and cheat sheets to keep open.