Which of the following is NOT a method to launch a Triggered Flow?

A Triggered Flow in Salesforce can be initiated through various methods. The methods include data changes, time-based triggers, and platform events. Each of these methods serves a specific purpose in automating business processes based on certain conditions or events.

When we consider data change, this refers to scenarios where changes in Salesforce records (like creating, updating, or deleting) can trigger a flow. This is a fundamental aspect of how flows react dynamically to data state changes.

Timing triggers allow flows to start at a predetermined time or after a defined delay. This can be useful for reminders, follow-ups, or scheduled tasks that need to occur after a data change.

Platform events are a powerful way to trigger flows in response to external events. When a platform event message is published, it can invoke a Triggered Flow, allowing for responsive automation based on real-time events occurring outside of Salesforce.

However, Apex code is not a valid method to trigger a Triggered Flow directly. While Apex can call flows programmatically using the Flow API, this does not classify as a Triggered Flow; rather, it is a method of invoking a flow from the logic contained within an Apex class. Consequently, Apex code stands out as the correct answer for the question regarding which option is not