The questions people ask before they install, and the ones they ask once the first scan comes back. If yours is not here, write to us and it will be.
Every active Flow, scored from 0 to 100 on the things that hurt in production: DML and Get Records inside loops, subflows, after save chains, missing entry criteria, element count, API version. Apex triggers are counted next to Flows when it ranks your objects.
Flows, Apex classes and triggers, validation rules, page layouts, Lightning pages, list views, matching rules, dependent formula fields and field level security. Standard fields included, not just custom ones, and each hit says whether it reads the field or writes to it.
Reports and email templates. It is a switch of its own because it opens every report one by one, which is slow on an org that has thousands. Run it before you delete a field for good.
It names the element at fault, not just the Flow. Once you have dealt with a Flow, hide that version from the riskiest Flows list: a new version comes back on its own after the next scan.
Yes. Export a PDF for one field, one object, or the whole org, the last one carrying the Flow analysis as well. Your name, your colour and your footer go on it, so it reads as your audit.
If you schedule it. The Flow Scanner and Field X-Ray each have their own schedule, and each sends a summary email with the score, the move since the last run and the top risks.
No. To read your metadata, the package only talks to your own org. Nothing is sent anywhere else, ours included.
No. Untanglr reads metadata: Flows, Apex, fields, layouts, permissions. It never queries an Account, a Contact, or anything else your users typed in.
Your key carries its own proof that it came from us. The package checks that proof by itself, inside your org, so it works with no connection to us at all.
Your account, the org domains you activated a key for, and the keys themselves. No scan result, no metadata, no record.
No. Untanglr reads metadata your org already holds. There is nothing to buy from Salesforce and nothing to switch on first.
Install as an administrator, then assign the Untanglr Admin permission set. A scan runs under the permissions of whoever started it, so without that set it runs and finds nothing.
A few minutes on a large org. The ones after that are quicker, because only what changed since the last run is read again, deletions included.
No. Before each release we upgrade an org with a live schedule, and both the job and the scans already recorded come through untouched.
No. Past scans, the Flow versions you hid, your branding and your settings all survive the upgrade.
Either, and it is the same package in both. Sandboxes sign in through a different Salesforce address, so the install link is the only thing that changes.
Yes. The package installs and runs without a key, with limits: one Flow scan a day, one Field X-Ray index an hour, and at most three recommendations shown. A one off seven day trial key shows every recommendation, with the same scan limits.
Not in what it unlocks. Both give you Premium, with every feature, the schedules and the summary emails included. The subscription is for your own org and renews every year. Keys are bought once, one per client org, and each runs for a year from the day you activate it.
One org for one year, sandboxes included. The key is tied to the production My Domain, and Untanglr traces a sandbox back to the org it came from, so the same key works in both with nothing to do.
Between a production org and its own sandboxes, there is nothing to move: the key already covers them. A genuinely different org is a different domain, so it needs its own key.
An unused key stays usable for three years from the day you bought it. The year only starts counting when you activate it on an org.
Nothing breaks and nothing is deleted. The app falls back to the free limits, and lifts them again the moment you paste a new key.
No. One account, and one key per client org. Your dashboard lists every org you activated, with the date each licence runs to.
Ask us directly. A real person reads it, and the answer usually ends up on this page.