Missing nulls/empty checks after lookups in Flows

Flows that perform record lookups should make sure that the records are found. Not performing such a check may cause the Flow to break.

Decreased operational efficiency, increased potential for human error, delayed time-to-market, and decreased employee satisfaction.

Is your Salesforce solution affected by Missing nulls/empty checks after lookups in Flows?

Clayton detects anti-patterns and offers automated fix advice to kickstart your Well-Architected journey.

How common is this issue?

16%

lower

How long do organizations remain exposed before fixing the problem?

59%

shorter

Easy

Automated

Data Integrity

Error Handling

Found a mistake?

If you think something is incorrect, missing or misleading please let us know.