App Startup Trigger

This trigger allows you to execute flows before other triggers in the app are started. It can be used to specify initialization logic that is specific to an app. For example, this trigger can be used for:

• Setting data or cache for later use in other flows
• Initialization of a database (insertion or extraction of data from tables)

Design considerations

• You can add one or more App Startup triggers to an app.
• You can add the App Startup trigger along with the Receive Lambda trigger, AWS API Gateway trigger, and S3 bucket Lambda trigger. You cannot add any other trigger along with the Receive Lambda trigger, AWS API Gateway trigger, and S3 bucket Lambda trigger.
• The trigger supports multiple handlers. So, you can configure more than one flow in a trigger.

• The flows are executed in the order in which they are configured in the trigger.

• The trigger is executed for all instances of the app. For example, if you scale up multiple instances of the app, the trigger is executed on each scale-up.
• If a startup flow fails, the engine is terminated.

• In container deployments, collective execution time of all flows configured to this type of trigger must not exceed startup time set for the app.