hi @Urs_Boller, I was able to reproduce your issue by giving the "partition key path" any value other than "/partitionKey". I think you have to set this exact value to make it work. See screenshot.If you want to customize this path, there might be a way in the Files SDK. But I'm yet to look into it.

Hi @Urs_Boller , I managed to init the State SDK and write / read operations with this.const state = await stateLib.init({ cosmos: { endpoint, masterKey, databaseId, containerId, partitionKey } })My "endpoint" value is like https://<tenant-name>.documents.azure.com:443.Do you have the same?

Hi @Urs_Boller , thanks for raising this question, a very nice one.Currently there is no Launch "callback" definition OOTB in Firefly, but we will forward the request to the respective team for consideration.What you could do for now, is to create a web action as a receiver of this callback. It is p...

Hi @keilorblend360 , the alarms are scheduled in UTC timezone. I hope it should have been fired at the correct time then? Otherwise, please let us know.

+1 to what Marijn said, please verify `.wskprops` file in your home folder to assure that the Runtime credentials are set correctly. And make sure "APIHOST=adobeioruntime.net"

Hi @Urs_Boller , the default timeout of an action is one minute as you observed. As you are running an async invocation, you can increase it to max 30 minutes.To do it, specify the desired timeout in your manifest file, as below:actions: generic: function: actions/generic/index.js runtime:...

Hi Urs - thanks for the update. Glad to hear!

Hi @Urs_Boller, actions are essentially invoked in the same manner after you do `aio app run` and `aio app deploy`. Only difference is that if you change something in the code and save while in run mode, it automatically re-deploys the action.Coming to your question about debugging, the logs should ...

Hi @Urs_Boller , thanks for the issue report. We have an github issue for tracking purpose here: https://github.com/adobe/aio-lib-ims/issues/55. We are prioritizing the fix and will update here when it is fixed.

hi @Urs_Boller  - here are my test values. Worked fine.startDate: "2020-08-31T14:20:00.000Z" stopDate: "2020-08-31T14:22:00.000Z"