Issue with 'Move Row' Automation

I have a Risk Log with the 'Move Row' automation. The intent is to move rows on the 1st of each month if a risk is closed and the 'Date Closed or Resolved' is more than 2 years ago.

When the automation ran recently it moved a closed risk dated 12/12/24, which shouldn't have moved since it's not more than 2 years ago.

Does anyone have any advice on what I may have set-up incorrectly with the automation? I've added screenshots to show the set-up.

Find more posts tagged with

Automations

Workflows in Smartsheet

Accepted answers

Paul Newcome

At this point, I would suggest reaching out to Support.

All comments

zealvert

@WMS Can you check and conform if there are no other workflows with a logic that overrides this one? Then only can we dig deeper on this.

Best

WMS

@zealvert I've checked and there aren't any other workflows with a logic that overrides this one. There are only two other workflows and both are simply alerts sent (a) once a month as a reminder to review and update the Risk Log, and (b) when rows are added or changed, the sheet Admin is notified.

Andrée Starå

https://community.smartsheet.com/discussion/141205/issue-with-move-row-automation

Hi,

I hope you're well and safe!

Strange!

If you haven’t already, I recommend submitting a support ticket through the new Smartsheet Support Portal.

I hope that helps!

Be safe, and have a fantastic day!

Best,

Andrée Starå | Smartsheet Expert Consultant & Partner / CEO @ WORK BOLD

✅ Did I help answer your question/solve the problem? Please support with💡 ⬆️ ❤️, and/or ✅ Answer. This will make it easier for others to find a solution or help answer! I appreciate it, thank you! 🙏

Paul Newcome

Change the formatting for the date in the sheet that that row currently resides in. Is it possible that 1924 was accidentally used for the year instead of 2024? Are you sure it was the automation that moved the row and not a user?

WMS

@Paul Newcome These are good suggestions. I confirmed the date column is formatted for dates and it is 2024 (not 1924). I'm checking to confirm the risk was included in the batch auto-archive on the 1st. If it wasn't then I guess I need to figure out who decided to take the (wrong) initiative and manually archive it!

WMS

@Paul Newcome I've confirmed it was in fact the automation that moved the row and was not a user. I'm concerned I can't trust the automation to correctly move rows to the archive log.

Any other suggestions?

Paul Newcome

At this point, I would suggest reaching out to Support.

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, sort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.