Get support

We're a small team and we read everything.

Contact us

• Support and questions: support@loupeapp.net
• General inquiries: hello@loupeapp.net
• Not a customer yet? Get in touch to set up a Loupe organization for your company.

Reporting a problem

When reporting a problem, it helps a lot if you include:

• what you were trying to do, and what happened instead
• the M3 environment(s) and company/division involved
• a screenshot of any error message
• your Loupe version, from Settings → About Loupe (or Help → About Loupe on Windows)

For a failed automation, the Latest response log of the failing step shows the exact M3 error for each transaction. Copying the JSON of a failed transaction from there is the fastest way for us to help.

Common questions

I signed in but see no environments. Your Loupe administrator needs to tick the environments you may use under Settings → User management. See Set up your organization.

Loupe says I've been logged out. Your Loupe session expired. Sign in again with your Microsoft account; your M3 environment sign-ins are kept.

A compare only shows 10 000 rows. That's the per-side limit. Add filters to narrow the result.

Loupe lost connection. If Loupe can't reach its servers, an overlay says so and offers Reload Loupe. Check your network connection; the overlay disappears as soon as the connection is back.

Where does Loupe keep its data? History for API runs, field values and automations is stored on your computer, in the Loupe application data folder (%APPDATA%\Loupe on Windows, ~/Library/Application Support/Loupe on macOS). Only your saved configurations, such as compares and collections, are stored on Loupe's servers; results from M3 are not.