@duypnguyen thanks for confirmation and link to the issue. I hope there is a fix soon ...

I try to create an adobe access token in a headless action. first I tryed to use aio-lib-ims but this fails to include in the action (maybe an issue with the core library and their dependencies?) is there any easy way to create an adobe access token having all data in the .env file?

thanks a lot! will think about this solution with npm and give it a try. maybe we keep things simple and just write single actions doing one thing at a time...

@duypnguyen thanks for the params, need to write them the right way! will give it a try. I will close the question as I think it will work

@SarahXu thanks for confirmation. Indeed, as soon as I run "aio app deploy" it works...

@duypnguyen here is my current setting: start-date: "2020-08-31T11:00:00.000Z" stop-date: "2020-08-31T12:00:00.000Z"so the interval should have run only for 1 hour .... and I knwo I entered the start time the right way (but it started before...)what are the right params for start ...

@duypnguyen just realised that my "interval" action does not stop (ignoring the param "stop-date". do you know what the key is to stop the alarm?

@duypnguyen and thanks for confirmation about security concerns, it looks as it is exactly what we are looking for (running an action in background doing all the stuff)

@duypnguyen I don't want to access the same action from both triggers (interval) as well as UI - it was just my first idea during testing. What we do now is having a backend action (headless action) which is triggered by whisk/alarms and the UI just displays the result. If we want, we can pass setti...

Hi @duypnguyen thanks very much - worked perfect and rule is triggered/running as expected!! that is really awesome just two more questions:Is it correct that without the attribut "web:yes" the action can't be accessed from anywhere, only used by triggers and events? so there is no way from outside ...