Flow Launcher Plugin Not Working: A Focused Checklist

Plugins and comparisons · Published October 30, 2026 · Publisher: flowlauncher.app

At a glance

For a failing Flow Launcher plugin, check its enabled state, action keyword, configuration, runtime, and remote service in that order. Verify that built-in app search still works. This keeps an extension failure from turning into an unnecessary full-profile reset.

Steps to follow

Find the plugin in Settings and confirm it is enabled. Type ? to inspect the active keyword instead of guessing it.
Run the simplest example query from the plugin’s instructions. Avoid testing with a complex personal workflow first.
Inspect required Python or Node.js paths, account settings, and any service connectivity. Test the service outside Flow when relevant.
Reload plugin data, record the exact error, and compare plugin and Flow versions with the maintainer’s requirements.

Check the result

A minimal documented query succeeds, or you have isolated the failing layer and captured a reproducible error without changing unrelated settings.

Limits and common pitfalls

Do not post API keys, access tokens, private filenames, or a complete unredacted UserData folder in a public issue.

Make the check repeatable

A useful issue report identifies the plugin by name, author, and version, followed by Flow version, Windows build, the harmless test query, and the relevant error text. Include whether disabling and re-enabling the plugin changes the result. This is more actionable than a screenshot of an empty list alone.

Questions and answers

Should I reinstall Flow when only one plugin fails?

Usually start with that plugin. If basic app search and other plugins work, investigate the extension’s own requirements first.

Sources and scope

Documentation-based guidance, with source review on October 30, 2026. What was and was not tested.

Related guides

Plugins and comparisons