Docs

Limits

Where Flow Companion can't read a flow, and what it doesn't do.

Where it can't read a flow

Orgs with API Access Control block the extension.
Orgs behind Microsoft Defender for Cloud Apps, or another corporate proxy that blocks extensions. The panel shows Not supported behind this proxy.
Users without the API Enabled or View Setup and Configuration permission. The panel names the permission to check.

The flow as last saved. Unsaved changes on the canvas aren't included. Save, then click the Refresh icon at the top of the panel.
This flow only. It doesn't read what's inside a subflow. To ask about one, open it in Flow Builder. It also doesn't read approval processes, other automation, records, or permissions in your org.

Flows too big for the model you picked. The panel says so before you can ask, and no question is sent. It names a model that can read the flow, with a button to switch. If none of your provider's models can, it suggests another provider. Nothing in the flow or the chat is trimmed or summarized to make it fit.
Rate limits. New API keys often start with a low limit, and a large flow or several quick questions can hit it. The panel shows Rate limit reached. Wait a minute, then click Retry. If it keeps happening, the card links to your provider's site, which shows how to raise the limit. The extension never retries on its own.

Edit your flow. When you ask how to change something, it describes the change and names the element. You make the edit in Flow Builder.
Scan flows against a fixed set of rules.