Due date automation has stopped working, despite no changes made. Why?

[Gemma]

I've had an automation set up for well over a year that's worked perfectly (I've changed some wording to protect data):

the moment a card in list "Renewal due" is due, post comment "@userx, {cardname} is due for renewal within the next 30 days. Please can you confirm if you would like to renew and for how long?"

This coincides with another rule which moves the card on its due date and sends a similar email to another user. However, this month, the rule rule above no longer works despite no changes being made.

Before I go ahead and just add the comment to the coinciding rule, I wanted to check if anyone else has experienced this issue and know how to fix it?

[Dreamsuite Mike]

Have you changed timezone at all?

I have seen strange behaviour before where there is a disconnect between the time the automation returns as a variable and the due date which caused some due date commands not to work.

You can do a test by making a button.  "Post comment {isodatetime}"

[Gemma]

No, not even a change of town when I log on/off, so not sure why this would happen.

I'll try the test you suggested, thanks

[Gemma]

I've created the button and done a check on a couple of different boards (including the affected one) and they all seem to be perfectly in time with my time zone

[Dreamsuite Mike]

Just reading your comment back, I wonder if it is more related to the sequencing of the 2 commands.  Us as users have very little control in the order of execution of these commands.  If command 2 executes before command 1, command 1 wont run.  Although it doesn't answer why it has changed, I would advise you either merge into 1 command or create a condition in command 2 that prevents it running before command 2 (like a comment containing, a label, a custom field)... 

[Gemma]

Yeah, I would have thought it was the sequencing too if it hadn't been working seamlessly for over a year. I get the feeling that some kind of update has been done and that's inadvertently messed with some of the automation (had that happen before with other Atlassian products, so it wouldn't be too surprising).

I suppose I'll cut my losses and merge the commands rather than waiting for a fix. Thanks for your help :)