Hi @Urs_Boller , it is recommended to leverage the openwhisk npm to programmatically call actions, triggers, etc.In terms of implementation, there could be a few ways to achieve what you need:- If you only want to invoke one action when the condition is met, you can invoke that particular action onl...

@Urs_Boller, the alarms are run in UTC. Did you set your stopDate in UTC?

Ah ok, that's good to know. Great idea! Then your scheduled action doesn't have web exposure, only being triggered then saving data to the state lib. And your "display UI" action would have `web: yes` to return the data to the UI.

Hi @Urs_Boller.Yes that's right, without `web: yes` your action can only be invoked by a trigger or directly by you in command line (aio runtime action invoke). Not possible to trigger from outside. IMO it makes sense from a security perspective, because you are assured that there is only one entry ...

Hi @Urs_Boller, here are answers relevant to your questions.Answer 1: It is not possible to deploy an alarmed trigger in `--local` mode, because the alarms provider and packages are not deployed in your local openwhisk. You have to deploy it on I/O Runtime (without `--local`).Answer 2: I tried the s...

Hi @Urs_Boller, in that case you first need to remove the web-src/ folder to make your app headless instead of SPA, so that JWT token can be validated. aio app delete web-assets To test the token, you could retrieve it from I/O Console, under "Generate JWT token" in your project, and pass it in the ...

Hi @Urs_Boller , first of all it would be good to identify whether your app is an SPA or headless, as described in the Security Overview . I assume you have the `require-adobe-auth` flag set to true for your actions.If it is an SPA, the user token must be passed from the Adobe Experience Cloud (ExC)...

@Urs_Boller, the returned payload of your first action would be in the input params of your second, and so on. The returned output of the last action in the sequence would be its response payload in the end.

Good discussions over here. Chaining of action in I/O Runtime (or Openwhisk at its core) is called sequence, which you can read more about here: https://github.com/AdobeDocs/adobeio-runtime/blob/master/reference/sequences_compositions.md#sequencesExample of sequence definition in the manifest.yml of...

Hi @Urs_Boller , the .env file is to defined the environment variables at build time. If you want to use them in the actions, you need to pass those variables to the actions via default parameters. To do the mapping, in manifest.yml, for each action there is an "inputs" section. You could simply map...