6 Smartsheet problems you can fix yourself, no support ticket needed

Scroll through the Smartsheet Community forum for an afternoon and the same handful of problems keep resurfacing. Most of them aren't bugs, they're gaps between how a feature is named and how it actually behaves. Once you know the mechanism, the fix takes two minutes. Here are six of the most common, dug up from real community threads.

1. My automation isn't triggering

This is the single most repeated post on the forum, and it almost always comes down to one detail: what actually changed the cell.

Smartsheet automations are built to react to a person doing something, a form being submitted, a manual edit, a status dropdown changed by hand. What they are not built to react to is a change that arrived indirectly, through a cross-sheet formula, a cell link, or another automation. If your trigger column is populated by a formula that pulls a value in from another sheet, an automation watching for "when this column changes" may simply never fire, because as far as Smartsheet is concerned nothing was "changed", it was calculated.

The fix: switch the automation's trigger type from a change-based trigger to a time-based one, "when a date is reached" or a recurring daily trigger, with your row conditions checking the current value of the column rather than waiting to detect a change in it. Because a time-based trigger runs on a schedule and evaluates whatever the cell currently holds, it doesn't matter that the value arrived via formula or cell link, there's no "change event" for it to miss. This is the standard workaround Smartsheet's own documentation gives for this exact restriction, and it's what the community consistently converges on: cells containing cross-sheet formulas or cell links are deliberately excluded from triggering workflows that modify the sheet (move row, lock row, record a date, and similar), to prevent infinite loops, so a change-based trigger on that column will never fire, no matter how correctly it's configured.

If the workflow looks correctly configured and still won't fire, don't just wait it out. Temporarily swap the action to something highly visible, like "change cell value" on a spare column, and re-test. That isolates whether the problem is the trigger criteria or the delivery of the resulting notification, which are two different fixes.

2. VLOOKUP stopped working and gives a #REF error

You built a VLOOKUP, it worked fine for weeks, and then one day it returns the wrong value or an error, without anyone touching the formula itself.

The reason is structural. VLOOKUP finds a value in one column, then counts across a fixed number of columns to grab the result: "column 4 from the left", for example. That column count is baked into the formula the moment you write it. If someone later adds a column, removes one, or reorders the columns, the formula still counts the same number of columns over, it just lands somewhere else. Smartsheet has no way of knowing the layout changed underneath it.

The fix: rebuild the lookup using INDEX and MATCH instead. INDEX/MATCH references the target column directly by name rather than by position, so it keeps pointing at the right data even if the source sheet's structure changes around it. It takes one extra step to write the first time, but for anything referencing a sheet you don't fully control, or a sheet that changes over time, it removes this entire category of failure. This is exactly the trade-off the Smartsheet community consistently lands on, VLOOKUP for a one-off lookup on a sheet that never changes shape, INDEX/MATCH for anything that has to survive real-world editing.

Check this Smartsheet article on the 3 look-up formulas to learn more about them: https://www.smartsheet.com/content-center/best-practices/tips-tricks/3-formulas-look-up-data-smartsheet

3. COUNTIF returns 0 on a multi-select dropdown, even though the value is clearly there

This one catches almost everyone the first time they build a summary metric against a multi-select column.

Plain COUNTIF checks whether a cell equals a value exactly. A multi-select cell rarely equals just one thing, it usually holds several selections stored together in the same cell. So a cell containing "Red, Blue" will never match a COUNTIF looking for an exact "Red", and the formula returns zero even though the data is right there in front of you.

The fix: use the HAS function, which was built specifically for this. It checks whether a cell contains a given value, regardless of what else is selected alongside it.

=COUNTIF(range, HAS(@cell, "Red"))

Two things worth knowing if HAS still comes back with 0:

• Inside a Sheet Summary field specifically, @cell needs to be typed in lowercase, capitalised versions aren't recognised there the way they are in a normal sheet formula.
• HAS looks for an exact item match within the cell's selections. If you need partial text matching instead (for example matching "App" inside "Apple"), that's what CONTAINS is for, but be aware CONTAINS will then also match unrelated values that happen to share those letters.

4. "Unable to create cross-sheet reference, maximum number reached"

This error confuses people because the numbers don't seem to add up. Smartsheet documents a limit of 100,000 referenced cells, and your references individually look nowhere near that.

The detail that's easy to miss: that limit applies per sheet, cumulatively, across every reference on it. If you have seventeen separate cross-sheet references each pulling in 6,000 cells, that's over 100,000 combined (17*6000 = 102,000), even though no single reference comes close on its own.

The fix: split the source data across two sheets instead of one, so each stays under the limit individually, then bring the data back together with direct cell links into a single consolidated metrics sheet. It's more setup than a single sheet, but it sidesteps the ceiling entirely.

Sometimes there is no obvious fix for this and you need to think creatively on how to reduce the number of cross-sheet references.

One more thing worth knowing if you're actively deleting references to make room: they don't always disappear immediately. On larger sheets it can take until the following day for a deleted reference to fully clear on Smartsheet's side, so if you're right at the limit and it still won't let you add a new one, that's often the reason, not a mistake on your part.

5. VLOOKUP or MATCH can't find a value that's obviously in the range

The value is sitting right there in the source sheet, but the formula insists there's no match.

Before assuming anything is broken, check for the boring explanations first, they account for the vast majority of these threads:

• a trailing space or invisible character in either the lookup value or the source cell
• a text-formatted number being compared against an actual number (or vice versa)
• the lookup value living in a formula-calculated cell rather than a typed one, which can carry a different underlying type than it visually displays

The fix: retype the lookup value directly rather than trusting a copy-paste, and rebuild the cross-sheet reference from scratch rather than editing the existing one. If the source column is itself a formula result, wrap it in a VALUE() or text conversion to normalise the type before comparing. If you're still stuck, switching to INDEX/MATCH won't fix a genuine data mismatch, but it does remove reference-position issues from the list of suspects, so it's a useful way to narrow down what's actually going on.

6. I set up a notification but I'm not receiving it 

You build a workflow, test it by making the triggering change yourself, and nothing arrives in your inbox. The workflow itself is usually fine, it's a personal setting getting in the way.

By default, Smartsheet can be configured to exclude your own edits from the notifications you receive, on the logic that you already know what you just changed. That's convenient for day-to-day use, but it means your own test of a brand-new automation may go completely silent even though the workflow is working exactly as built.

The fix: go to your account's Personal Settings and check "Include my changes in sheet notifications". This is specifically called out as the setting to enable while testing automations, and it's the first thing worth checking any time a workflow seems to fire but nothing shows up. If you want the opposite long-term, notifications on for the team but not for your own edits, that's normally handled differently, either by leaving that box unchecked, or by adding a condition to the workflow itself that Modified By does not equal you.

None of these need a support ticket. They're mechanism issues, not outages: multi-select columns need HAS instead of COUNTIF, VLOOKUP is position-based and will drift, cross-sheet limits are cumulative per sheet, and your own notification settings can exclude your own tests. Once you know which mechanism is at play, the fix is usually a formula swap or a checkbox, not a wait for someone else to look into it.