The Timer start event is designed to trigger an integration flow based on a schedule. A key configuration option for the Timer event is the "Run Once" scheduler. When this option is selected, the integration flow is executed immediately after it is successfully deployed. This feature is specifically intended for scenarios where a process needs to run a single time, right at the beginning of its lifecycle on the runtime node, without waiting for a future scheduled time or an external trigger.

A. Content Modifier: This is a message processing step used to modify the message body, headers, or properties. It does not initiate an integration flow.

B. Router: This is a routing element that directs a message to different paths based on specified conditions. It operates within an already running flow.

C. Message Digest: This is a security-related processing step used to calculate a hash value of the message content to ensure data integrity. It is not a start event.

1. SAP Help Portal

Cloud Integration - Define Timer Start Event: "To schedule the execution of an integration flow

you use a Timer start event... The Scheduler tab allows you to specify when the integration flow is to be executed... Run Once: The integration flow is executed immediately after deployment."

2. SAP Help Portal

Cloud Integration - Content Modifier: "The Content Modifier allows you to change the content of a message... It is a message processing step." (This confirms it is not a start event).

3. SAP Help Portal

Cloud Integration - Router: "A router is a routing step that allows you to branch the integration flow... based on certain conditions." (This confirms it is a routing element

not a start event).

4. SAP Help Portal

Cloud Integration - Message Digest: "The Message Digest step allows you to create a digest of the incoming message..." (This confirms it is a processing step for security

not a start event).