Major Move Row Automation Issues – Duplicate Rows & Cell History Lost

Question

Has anyone else noticed issues with Move Row automations over the last few days, particularly around 8/19? I'm seeing two major issues that may be related:

1. Rows being duplicated when moved: We have an automation that moves a completed row from an Open Work Orders sheet to a monthly sheet. I'm finding a TON of duplicates in the destination sheet — in one case, the same row was moved 41 times when it should have moved once. Cell History on those duplicates indicates Smartsheet Automation moved them on 8/19, at varying times. Testing the automation now, it seems to be moving rows only once as expected.

2. Cell History is no longer retained after a row is moved: Historically, when a row was moved via automation, the destination row retained its full original Cell History — previous values, who made each change, dates/times, PLUS an entry showing when the row was moved from another sheet.

Now, after a row is moved, that history disappears. The Cell History only shows the most recent cell value, dated at the time the row was moved, with Smartsheet Automation shown as the person who made the change. It no longer shows the original changes/users OR the "Row was moved from another sheet" entry.

I reproduced the Cell History issue with a controlled test today, and I'm seeing it in both Grid and Table View.

I've submitted Support tickets for both issues. Is anyone else seeing either of these behaviors?

beckyb27 · Answer

@Shawn M. - we had issues with duplicate notifications being sent all through August. It appeared to get better in the last few weeks, but just this weekend sent multiple duplicate automation notifications. Is this the result of the workflows being "reverted to run on our proven, stable engine configuration"?

Shawn M. · Answer

We want to give our Community a clear update on the recent Automations issues some of you have reported — both workflows that didn't fire when expected, and cases where notifications or updates fired unexpectedly.

We've identified the root cause tied to changes we recently made. Our team has completed a thorough investigation and confirmed the underlying issue.

In the meantime, we've already taken action to stabilize things — affected workflows have been reverted to run on our proven, stable engine configuration, so you shouldn't need to take any action on your end right now.

We're actively developing a permanent fix and expect to roll it by late next week. Our team is treating this as a top priority.

Thank you for your patience and trust as we work this through!

Rae Ann Harris · Answer

From reading some of the other posts, it appears that when they fixed the problem, it retriggered automations.