Understanding Run Stopped Rows in Data Table at Row 556

Clay team - Can you help me understand why I have a bunch of rows showing "Run Stopped" starting at row 556 in this table?

9 comments

Andrew T.
·
·
https://app.clay.com/workspaces/10648/workbooks/wb_ZNVVsQ2DGUAf/tables/t_3GapYvw9QHvM/views/gv_ZfX96K4ycE9x
Clay
APP
·
·
"Run Stopped" status typically occurs when a column run was interrupted or stopped midway through processing. This often happens if the column was changed multiple times, updated, or if the run was manually stopped. To resolve this, create a new column by duplicating the current one and run it on the remaining rows. Filter for rows where the current column "is empty," then run the AI on those rows. Afterward, use the "merge columns" feature to combine the results. You can also try running specific rows by right-clicking the column, hovering over "Run Column," and selecting "Choose Number of rows to run" to specify starting from row 556.
Source: Run Options
Mark L.
·
·
Hey Andrew, when a column/table is running, at the bottom right corner of the screen appears a "Stop updates" button. The "Run Stopped" status results from using that button. Did you have other questions on your table here?
Andrew T.
·
·
I've used that before, but this is a table that just runs in the background, so I didn't use that for these rows. Any other ideas?
Mark L.
·
·
Those cells were last updated in mid-January, so unfortunately we no longer have logs that will tell us more, not in that level of detail. I can say that I have never seen that status outside of a manual stoppage, and the cell status we have behind the scenes is ERROR_ACTIONS_STOPPED_BY_USER, which would correspond with that action.
Andrew T.
·
·
Yeah, I've seen that when I stopped a run, but I just got back from being out of office and no one else in our org has access to our account... 🤔
Tanvi R.
·
·
Hey Andrew, it's hard to say what happened here since the timeline is ~6 months ago. However, another reason sun stopped could've occurred is if auto-update was on and then turned off in your table. Let us know if you're seeing this issue in any recent tables/runs and we'll have more information to investigate
Andrew T.
·
·
Thanks. I think I have what I need here.
Tanvi R.
·
·
Great! I'll close this out for now but don't hesitate to reach back out if anything else comes up.
👍1

Understanding Run Stopped Rows in Data Table at Row 556 | Clay