Skip to main content
Solved

Conditional step triggers too early because of GMT

  • September 19, 2024
  • 4 replies
  • 0 views

Forum|alt.badge.img+11

My automation has a conditional step that runs if these conditions are met:

{Date Assigned GMT} is on or after 10/01/2024 AND
{Date Assigned GMT} is on or before 10/31/2024

I am located in the Eastern Time Zone. I am aware that automations do everything in GMT.

How can I prevent this step from running until it is really 10/01/2024 in Eastern Time?

 

Best answer by TheTimeSavingCo

Jean_Thoensen wrote:

Thanks for your suggestion, but this is a problem with a conditional step within the automation itself, not the trigger. The trigger is driven by a non-date event. This conditional step, which sends an email, should only happen during certain times. That’s why we have a conditional group at the end of the automation—if we’re within a certain window, only then send an email.


What if you used a formula field to figure out whether it's within the window you want and use the conditonal on that instead? 

View original
Did this topic help you find an answer to your question?

4 replies

TheTimeSavingCo
Forum|alt.badge.img+28

Perhaps you could try a "When record enters view" trigger instead?  It seems like the view filters respect timezones so that may work


Forum|alt.badge.img+11
  • Author
  • Known Participant
  • 20 replies
  • September 20, 2024
TheTimeSavingCo wrote:

Perhaps you could try a "When record enters view" trigger instead?  It seems like the view filters respect timezones so that may work


Thanks for your suggestion, but this is a problem with a conditional step within the automation itself, not the trigger. The trigger is driven by a non-date event. This conditional step, which sends an email, should only happen during certain times. That’s why we have a conditional group at the end of the automation—if we’re within a certain window, only then send an email.


TheTimeSavingCo
Forum|alt.badge.img+28
Jean_Thoensen wrote:

Thanks for your suggestion, but this is a problem with a conditional step within the automation itself, not the trigger. The trigger is driven by a non-date event. This conditional step, which sends an email, should only happen during certain times. That’s why we have a conditional group at the end of the automation—if we’re within a certain window, only then send an email.


What if you used a formula field to figure out whether it's within the window you want and use the conditonal on that instead? 


Forum|alt.badge.img+11
  • Author
  • Known Participant
  • 20 replies
  • September 23, 2024
TheTimeSavingCo wrote:

What if you used a formula field to figure out whether it's within the window you want and use the conditonal on that instead? 


I think that would work better, @TheTimeSavingCo. Thank you for the suggestion.


Reply