Which flow type(s) can be called by another flow?

The correct choice encompasses both Autolaunched and Screen flows, which can be invoked or called by another flow.

Autolaunched flows are designed to run in the background, often triggered by processes, buttons, or other automated means. They do not require user interaction, which makes them suitable for a variety of use cases, including integration with other flows. For instance, one Autolaunched flow can call another to perform a specific task or logic, thus enabling complex operations while maintaining modularity.

Screen flows, on the other hand, are designed for user interactions and can also be invoked by other flows. This allows them to be part of larger processes where user input is necessary at specific stages, offering a seamless experience for users being guided through multi-step processes.

Together, these flow types provide flexibility in structuring and orchestrating larger workflows within Salesforce, enhancing automation while accommodating diverse requirements for user engagement or background processing. Other flow types, such as Scheduled and Batch, serve specific purposes for running scheduled operations or processing records in bulk but are not designed to be invoked by another flow.