@Saif - in that case could you post this question in the Console forum: https://experienceleaguecommunities.adobe.com/t5/adobe-i-o-console/ct-p/adobe-io-console.

are you doing this on Adobe developer console?

As mentioned earlier, the cron triggers are based on UTC. So yes, if there is a daylight saving in your timezone, you would need to adjust the triggers.Wrt updating cron time, you're right it's not possible to update alarms feed once created. You could instead create a new trigger with correct time ...

Hi @Nikhil-Kumar - From the error logs, it seems you are using @adobe/aio-lib-state. Please note that, it is not possible to use wskdebug here because the debugger would create a local clone of the action which can not access the DB behind the State SDK (unless you configure it to use your cosmos DB...

Problem has been solved via DM. We will make some improvements for the codelab so that it's up to date with the generated UI from app template.

@In_Na - glad to hear you are following the code lab. It is actively maintained with up-to-date content. Which error are you getting exactly?

Hi @brijesht4727374 - glad to hear it worked! The rule turning into "inactive" could be a result of continuous failures when you first deployed the scheduled action. Hence it's worth checking if there's no activation after you deploy the triggers and rules.

@brijesht4727374 - please try `aio runtime rule enable everyMinRule` (shouldn't have added the namespace before the rule name).

Ok - it seems your rule is inactive. Could you try this command `aio runtime rule enable 34999-sfmctargetheadless-stage/everyMinRule`, and verify if the trigger runs every minute now?

Hi @brijesht4727374 - could you try this command `aio runtime list` to verify that all your actions, triggers and rules were deployed correctly? and that the rule is active?