nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Smartsheet Community

Connect with peers, share your expertise, and inspire what’s next in Smartsheet — from proven practices to practical how-to insights from fellow users and product experts.

Automation not triggering

jmaxbr

Hello Community, I am having issues with an automation not firing, not sure what is tripping it up:

Screenshot 2026-06-11 at 10.25.12 AM.png

Screenshot 2026-06-11 at 10.33.27 AM.png

Also I am unsure if I should see the Update Request icon highlighted in the left margin, when this fires? Of course if I manually click to send an Update Request, it does highlight, but I am trying to set this up so that it is just rolling along, triggering for everything that is 90 days out - I have two conditions because if there is a value in Confirmation, it means I've already booked that Accommodation so I don't need to request an update.

タグが付けられた投稿をさらに検索

Sheets

functionality

Automations

Accepted answers

Paul Newcome

The issue is with the trigger. If you trigger ON the date field, the date field will never be in the future.

Instead, click on where it says "Run Once" and change that to "Custom". From there you can set it to run daily (every one day), and leave your conditions in place.

jmaxbr

Amazing. I can see why now. I had assumed the 90 days in advance meant that it would continually trigger every day at 9am, but this makes more sense:

Screenshot 2026-06-11 at 11.02.45 AM.png

And the double condition presents no issue?

Paul Newcome

Ah. Ok. I misunderstood.

In that case, set your trigger back to being date based - "Run Once". Then you can change "on" to "90 days before" and select the check-in date.

Remove the date requirement piece from your condition block, and you should be good to go.

tannermullin

The reason the check-in date condition wouldn't give you what you want is that condition will pass for every single day that the check-in date is less than 90 days in the future.

Hopefully that explanation helps to understand that type of condition going forward.

All comments

Paul Newcome

The issue is with the trigger. If you trigger ON the date field, the date field will never be in the future.

Instead, click on where it says "Run Once" and change that to "Custom". From there you can set it to run daily (every one day), and leave your conditions in place.

jmaxbr

Amazing. I can see why now. I had assumed the 90 days in advance meant that it would continually trigger every day at 9am, but this makes more sense:

And the double condition presents no issue?

jmaxbr

As a follow-on from the Request itself: once completed, is there a way to change a status column if the Request has been updated? I might need to change the rows that I send out, or add a column, but it would have to trigger once a change has been made by the end-user, if that makes sense?

Paul Newcome

I'm not sure I follow.

jmaxbr

This sheet is for hotel/apartment accommodations. Here's my workflow: I bulk enter the individual contractor dates, however these often change and hence I built the above workflow to request updates from them once they have actually booked their travel, confirmed other assignments etc. However, once they complete the request, I don't think I have a way to know they've updated their dates, or if they've simply confirmed what's already there. Either way, I'd want their "status" to change from blank to "yellow" which would indicate I am good to book their hotel/apartment.

So my question above was, is there a way to indicate that they have EITHER made a change to dates, OR confirmed the existing dates are good? How would I accomplish that?

Paul Newcome

You could include a checkbox in the update request where they can check the box to confirm everything looks good

jmaxbr

Followup, here's the automation as it is set up now, and the second pic shows what I see when I click on the Request icon in the left margin - does this mean this individual is getting a request every day? I want the automation to fire one time, meaning to send one Update Request, 90 days out from when they are supposed to arrive at the hotel/apartment.

Paul Newcome

Ah. Ok. I misunderstood.

In that case, set your trigger back to being date based - "Run Once". Then you can change "on" to "90 days before" and select the check-in date.

Remove the date requirement piece from your condition block, and you should be good to go.

jmaxbr

I did not see those dropdown options for X days before/after. That looks much cleaner

Paul Newcome

Happy to help. 👍️

tannermullin

The reason the check-in date condition wouldn't give you what you want is that condition will pass for every single day that the check-in date is less than 90 days in the future.

Hopefully that explanation helps to understand that type of condition going forward.

Sign in to join the conversation!

クイックリンク

Component react.discussion.discussions had an error.

ref must be one of: categoryID, siteSectionID, category, category/categoryID, category/name, category/description, category/url, category/allowedDiscussionTypes, locale, siteSection, siteSection/basePath, siteSection/contentLocale, siteSection/sectionGroup, siteSection/sectionID, siteSection/name, siteSection/description, siteSection/apps, siteSection/attributes, layoutViewType, discussionID, commentID, page, latest, sort, sortType, lookupSort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.