Columns looked up by their title
How you'll know: A column called "Due" became "Due date" and the script started skipping that field, or writing to the wrong one.
Fix: Store column IDs, which don't change on a rename. Re-read the column list at the start of each run and alert if a column you depend on has gone.
The webhook ran out of retries
How you'll know: The webhook's status is disabled and events stopped arriving after your server had an outage.
Fix: Smartsheet retries a failed delivery up to 14 times, the last ones about three hours apart, then disables the webhook. Watch the status, re-enable it, and re-read the sheet to catch what changed in the gap.
A token from the wrong region
How you'll know: Every call returns an authentication error, but the token works when someone tests it in another tool.
Fix: Check which host the account lives on. A Smartsheet Regions Europe token only works against api.smartsheet.eu.
An old notice applied as if it were new
How you'll know: A row flips back to a value someone changed an hour ago.
Fix: Retried callbacks can arrive hours late. Since the payload only names the row, always read its current values from the API before writing anywhere else.
One row at a time
How you'll know: 429 responses on large updates, and runs that take far longer than they should.
Fix: Send rows in bulk. A bulk add or update counts as one request against the limit.