Flow Trigger Explorer in Salesforce won't display a record-triggered flow when either of the following is true:
This article explains why some Salesforce flows don't show up in Flow Trigger Explorer, and how to work around each cause.
For flows created prior to the Summer '21 release, you can work around this by saving the flow as a new version. This makes the flow visible in Flow Trigger Explorer. Once the issue is resolved, you can safely delete the new version, since it doesn't need to be kept. Note that this issue occurs intermittently, so results can vary between orgs.
In some cases, flows that come from a managed package may still not appear even after saving a new version. When that happens, this workaround may not fully resolve the issue.
Flow Trigger Explorer currently filters out flows categorized as templates. This is a product limitation, so any flow marked as a template will not appear in Flow Trigger Explorer, regardless of when it was created.
000396772

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.