- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
@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 settings to the headless action by using another action that sets some keys using aio-lib-state
Views
Replies
0 Likes
Total Likes