When working in an Experience Cloud site, what is a reason an admin can't see a particular flow to add that flow to a component on the site page?

The reason that an admin can't see a particular flow to add it to a component on an Experience Cloud site is that screen flows must be active to be available for sites. When flows are created in Salesforce, they can be in various statuses, including Active, Inactive, or Draft. Only flows that are in an Active status can be used in components on Experience Cloud sites. This ensures that users are not exposed to outdated or incomplete flows, enhancing the overall user experience.

While other aspects might influence the behavior of flows in different contexts or settings, the key point here is that the flow must be active for it to be utilized within the site. This focus on active flows helps maintain data integrity and ensures that users are interacting with the most current and reliable automation processes available.

In contrast, other potential reasons listed do not directly address the fundamental requirement of flow activation status. For instance, stating that only specific types of flows, such as screen flows and scheduled flows, are available does not capture the essential status requirement. Similarly, the need for multi-column flow layouts or the configuration for external distribution does not specifically determine whether a flow can be used on a site page.