Automation not working as intended to transfer isse from one status to another

[Ankit Bhandari]

I created an automation in jira work management, for company managed projects (in a dummy project). I want issues to be transferred from to do->Late as soon as they miss due date.

I observed that rule works fine for tasks that were created on that day and they miss deadline on that day, but suppose i created a task on 12th with due date on 12th. but now clock ticks to 13 and automation which is scheduled to run every 30 minutes did nothing in between 12-12:30am and the whole day. please check screenshot. I have also also attached the change history of issue and the rule as well. note I am super admin here, there's no restriction to move status from to do to late until you are admin of the project, im added in all of the projects as admin as well. if you have any alternative suggestion as well, i am open to that as well. product plan is premium

[John Funk]

Hi Ankit - Welcome to the Atlassian Community!

First, why are you running it every 30 minutes when you are just checking if it is today or not? 

Why not run it once a day early in the morning and check for the due date > startofDay(-1)

[Ankit Bhandari]

I have currently set it for 30 minutes to see log status of the tasks, if code checks out i would be setting to once a day

[Trudy Claspill]

Hello @Ankit Bhandari 

Welcome to the Atlassian community.

Concerning your answer to @John Funk 's question, you don't need to change the rule schedule to test it. In the upper right corner there will be an option to Run the rule so that you can run it immediately rather than waiting for the scheduled time.

Addressing your is with no action being taken on the 13th, I believe that @Rilwan Ahmed identified the cause with their response #2.

[Rilwan Ahmed]

Hi @Ankit Bhandari ,

Welcome to the community !!

1. Have you checked the Jira system time (https://<baseURL>atlassian.net/jira/settings/system/general-configuration) . Your system time is not necessarily be same as the Jira time. 
2. try unchecking "Only include issues that have changed since the last time this rule executed" in the rule "When" part