how to detect which column changed in onEdit using e.range.getColumn vs e.range.getColumnIndex

By Sai Kiran Pandrala · Last verified: 2026-05-31 · Source: community forums (r/nocode, r/automation, r/GoogleAppsScript, r/PowerAutomate, r/n8n, r/make, r/ClaudeAI), vendor status pages and changelogs, vendor help centers, in-product help

how to detect which column changed in onEdit using e.range.getColumn vs e.range.getColumnIndex on Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 comes up often enough in the r/nocode, r/apps, and adjacent automation communities that there is a stable fix pattern. The pattern I see most often is in Make for exactly this reason - last Tuesday I was mid-build for a client when this exact thing hit me, and the recovery path is mostly known, the vendor help just buries it under three layers of marketing copy.

What how to detect which column changed in onedit using e.range.getcolumn vs e.range.getcolumnindex actually involves on Google Apps Script, Sheets Automation with SpreadsheetApp, 2026

On Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 in my experience the most useful first-pass tools are Sheets API Explorer at developers.google.com, Google Cloud Console linked GCP project, clasp pull / push CLI. Each of these surfaces a different layer of the failure - keep at least the first one in your personal notes so the next time this happens you do not start cold.

For verification on Google Apps Script, Sheets Automation with SpreadsheetApp, 2026, the methods that survive contact with a real Monday-morning workload are SpreadsheetApp.flush() before reading back written values and Run > View execution transcript in the legacy editor. Anything less than that and you are shipping on vibes.

Authoritative sources for Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 that I cross-reference before committing to a fix: developers.google.com/apps-script/guides/sheets/functions, developers.google.com/apps-script/guides/triggers/installable, developers.google.com/apps-script/guides/services/quotas. Marketing blog posts and Medium writeups are signal, not ground truth.

The rest of this page is the structured fix path. Start with diagnose, then remediation, then the automation options so you do not have to do this by hand the next time it surfaces. Verify and safety sections at the end are the discipline that keeps the fix from regressing the next time you open the platform.

Identify

Second pass: open the Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 workspace admin or settings panel and look at the audit log or activity feed for the failing window. Most modern automation platforms surface an audit trail (the platform's execution history, the connector run log, the integration activity feed). The audit log tells you whether the failure was your action, a teammate changing a connected account in the same minute, or a platform-side rollout. Many "permission denied" or "connection not found" reports trace to a credential-level change pushed in the same admin panel in the previous hour - the audit trail makes that obvious without guesswork.

Third pass: read the HTTP status code and the in-product error message like an x-ray of your Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 session. 4xx is something on your side (auth, scope, payload, sharing), 5xx is theirs (or a shared infra fault). 401 = signed-in session expired or the wrong account is active, 403 = you are signed in but the connector is bound to a different identity, 404 = the URL points to a deleted or moved object, 409 = another run is touching the same record at the same time, 422 = the payload validates against schema but fails a workspace rule (required field, locked field, custom validation), 429 = rate limit on the trigger source or destination API, 5xx = retry after a minute. Cross-reference the in-product error string against the Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 help center because the same "something went wrong" toast can mean five different things on a single page. If the same action cycles between 429 and 503 over a tight loop, the API quota on the trigger source is exhausted - slow the scenario down or split it into batches.

Sixth: pin down the latency and reliability envelope on the Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 session under real working conditions. Run a long-duration sanity test by executing the failing scenario 10 times over 15 minutes, logging the timestamp and the result (success / error code / which step failed) per attempt to a notes file. Watch for the breakpoint where the success rate dips below 80 percent - that is your real signal that something is wrong, not the one-off failure that prompted the investigation. If you are on a marginal network (cafe wifi, mobile hotspot, hotel network), run the same test on a wired or known-good connection before assuming the platform is the problem. Capture the breakpoint in your personal notes next to the platform version, the account, and the workspace id - the next time this happens to a teammate, the notes are gold.

Field notes from real Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 incidents

My go-to verification step is `ScriptApp.getProjectTriggers().forEach(t => Logger.log(t.getHandlerFunction()))`; I learned the hard way that the Google Apps Script UI will happily lie about whether a flow really ran. Before I mark an Google Apps Script ticket resolved I always run `clasp logs --json` once more and screenshot the output, that habit has caught at least three silent regressions for me.

I keep ScriptApp.getProjectTriggers() listing docked on a second screen whenever I am building inside Google Apps Script; one glance tells me whether the run actually fired or silently skipped. In Google work, the cost of guessing is almost always higher than the cost of reading the Google Apps Script changelog, read the changelog first.

Tools I actually reach for

For most Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 stalls I start with Apps Script quotas dashboard for the user, fall back to clasp pull / push CLI, appsscript.json manifest inspector, Sheets API Explorer at developers.google.com when Apps Script quotas dashboard for the user cannot surface the answer, and keep V8 stack trace from Logger.log(e.stack) handy for the cases where neither answers. That ordering is not academic - it matches the layers of the failure as they tend to surface, so the cheapest signal lands first and the heavier tooling only comes out when the simpler answer does not hold up. My muscle-memory shortcut for this is to run the first tool while the failing screen is still open, not after I have already restarted the platform.

Verification I run before I call it fixed

Before I mark a Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 stall resolved, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheaper checks gate the more expensive ones.

Logger.log(JSON.stringify(SpreadsheetApp.getActiveSpreadsheet().getId()))

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

ScriptApp.getProjectTriggers().forEach(t => Logger.log(t.getHandlerFunction()))

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

SpreadsheetApp.flush() before reading back written values

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Logger.log(CacheService.getScriptCache().get('key'))

Only when every line above runs clean do I close the loop and update my notes with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 detail, the disambiguation order I lean on is stable. I usually check developers.google.com/apps-script/guides/triggers/installable for the ground-truth view on this part of Google Apps Script, Sheets Automation with SpreadsheetApp, 2026. I usually check developers.google.com/apps-script/guides/services/quotas for the ground-truth view on this part of Google Apps Script, Sheets Automation with SpreadsheetApp, 2026. I usually check developers.google.com/apps-script/guides/v8-runtime for the ground-truth view on this part of Google Apps Script, Sheets Automation with SpreadsheetApp, 2026. I usually check developers.google.com/apps-script/reference/spreadsheet for the ground-truth view on this part of Google Apps Script, Sheets Automation with SpreadsheetApp, 2026. Marketing blog posts and Medium writeups are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Solution-focused remediation path

For Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 integrations where rate limits or plan quotas are suspect, read the in-product hints honestly. "You have reached the limit for this workspace" usually means you hit an operation, task, or run cap on the current plan tier. "Slow down, you are sending requests too quickly" is the rate-limit signal on the trigger source or destination API. "This payload is too large" is the per-call cap. Each is telling you the exact same thing in a Google Apps Script, Sheets Automation with SpreadsheetApp, 2026-specific dialect. Apply exponential backoff for API-driven runs (base 1s, double up to 60s, retry up to 5 times) and split a large batch into chunks of 100 records at a time. Decision point: if you are hitting the quota sustained rather than in bursts, upgrade the plan tier or request a quota increase from the workspace admin with a written usage justification; without it, batch the work or shed load at the producer. Replay the failing scenario against a fresh test workspace at half the throughput to confirm the new safe rate before pushing to the real workspace.

Start by sorting the Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 failure into one of three buckets, because roughly 80% of cases fall here. Bucket one is auth / account drift: you are signed into the wrong account, the SSO session expired, MFA tripped, or the workspace owner changed your role. Bucket two is sync / cache drift: the platform has a stale view of the connector, the offline cache disagrees with the cloud, or a recent edit has not synced yet. Bucket three is plan / quota / sharing: the action requires a higher plan tier, the workspace hit an operation or task cap, or the connector you are trying to use was revoked. Pick the bucket first, then act. Before you act, capture a baseline screenshot of the failing run plus the run id so you can prove whether the fix actually moved the needle. Decision point: if the failure is intermittent and you are on a paid Business / Enterprise plan, open the in-product support chat first - vendor support on a paid tenant beats hours of speculative debugging on cost and on liability if the failure recurs.

When the Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 fault tracks to integration failures, automation delays, or webhook drops from the trigger source (the trigger source, the connector, the upstream provider), treat the integration plane as suspect. Open the integration log in the connected service (the trigger source's webhook log, the platform's connector run history) and read the response status the Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 endpoint actually returned - most "scenario not firing" reports are actually "webhook firing but the connector failed and the platform backed off." Verify the connected account is still authorized (the OAuth grant in Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 is not silently revoked) and that the trigger event is what you think it is. Decision point: if the trigger is firing but Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 is rate-limiting it, throttle the scenario (bump the polling interval, add a sleep module, enable batch mode) and re-run. Verify the connected workspace is the right workspace - a common foot-gun is the personal workspace being authorized while the work workspace holds the data.

Automate this fix so you do not do it twice

Fleet API token + OAuth grant rotation via vendor admin

Rotating a personal access token on one Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 workspace by hand is fine; rotating across a team of workspaces is how you end up with twelve different tokens, four expired ones, and an unknown blast radius. Drive rotation through the Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 admin SDK or REST under a service account with the rotation scope only, store the new token in a personal password manager (1Password, Bitwarden, vendor secrets manager) with versioning enabled, and roll the consumer scripts one workspace at a time with a health check between each. Pin the API version explicitly during rotation so a coincident vendor rollout does not look like a rotation failure.

# Rotate the platform API token (regenerate via the admin UI, capture in 1Password)
op item create --vault Work --category "API Credential" \ --title "apps platform token 2026-05-31" \ password="$NEW_PLATFORM_TOKEN" notes="Rotated $(date -Iseconds)"
# Capture the old token as deprecated so cutover is reversible
op item create --vault Work --category "API Credential" \ --title "apps platform token OLD 2026-05-31" \ password="$OLD_PLATFORM_TOKEN" notes="Old token marked deprecated"

Codify the platform version pin and rollback as a single notes entry

Once a stable platform version is identified for the Google Apps Script, Sheets Automation with SpreadsheetApp, 2026, write the version string, the build hash, and the workspace policy state to a personal notes entry with the date in the title. Reproducible rollback is then a single download-and-install plus a sign-in. Pin the workspace policy state explicitly so a vendor-side default change does not silently shift behavior under you. Stage the notes entry next to a checklist that lists the failing screenshot, the Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 incident id (if any), and the support case number; the second time the workflow breaks at 9 a.m. you do not want to be rediscovering which platform build was actually green.

# Personal notes template (apps)
Date: 2026-05-31
Platform: apps
Working build: 2.45.1 (Build hash: a1b2c3d)
Account: [email protected]
Workspace: ws-prod-apps
Failing screenshot: ~/notes/apps-2026-05-31.png
Support case: SUPP-apps-12345
Rollback path: download installer from vendor releases page, sign out, reinstall, sign back in

Multi-workspace rate-limit + retry policy via shared client wrapper

When the Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 integration runs across multiple workspaces or accounts, every consumer needs the same backoff, jitter, and idempotency behavior or one noisy workspace will starve the rest. Wrap the vendor SDK or fetch call in a thin client that reads the rate-limit headers (X-RateLimit-Remaining, Retry-After, x-ratelimit-reset), applies full jitter (base 200ms, cap 30s, max 5 retries), and de-dupes writes by a stable key (the platform's run id, the connector's external id, the destination record id). Emit simple log lines tagged with the workspace id so a quota burst on one workspace shows up in the same log as the downstream cascade.

# Python - apps API wrapper with full-jitter retry
from tenacity import retry, wait_random_exponential, stop_after_attempt, retry_if_exception_type
import requests class RateLimited(Exception): pass @retry( wait=wait_random_exponential(multiplier=0.2, max=30), stop=stop_after_attempt(5), retry=retry_if_exception_type(RateLimited),
)
def call_apps(method, path, token, payload=None): r = requests.request(method, f"https://api.example.com{path}", headers={"Authorization": f"Bearer {token}"}, json=payload, timeout=10) if r.status_code == 429: raise RateLimited(r.headers.get("Retry-After")) r.raise_for_status() return r.json()

Pitfalls to dodge

Read-only validation before any write is the single step most Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 fixes skip, and it is the step that lets you roll back when a fix backfires. Screenshot every existing settings page (the workspace settings, the sharing policy, the connected-apps list, the members page, the plan tier page), capture the failing screenshot in a notes entry, export the relevant log to CSV if the platform supports it (the platform's run-history export, the audit-log download), and screenshot the activity feed showing the failing window before any change. On Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 workspaces with multiple environments (test workspace, real workspace) record the platform version, the settings state, and the connected-apps list in each before toggling anything, because a "fix" pushed only to the test workspace is a known regression vector when the real workspace has a different policy.

The mirror-image mistake is confusing a user-side symptom with a vendor fault on Google Apps Script, Sheets Automation with SpreadsheetApp, 2026. A persistent 403 is often a connector-level change pushed by the workspace owner rather than a Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 bug. A "scenario not found" can be a moved scenario rather than a deleted one. A "webhook not firing" is frequently a corporate proxy or firewall dropping the Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 egress IP rather than a vendor-side regression.

Resolve

• Reproduce the original failing run against Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 on the same device AND a second device with the same account. If the failing toast or error code still surfaces on any device, you have not fixed it.
• Watch for 24 to 48 hours via the Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 workspace audit log + the integration history + your personal notes. Cached error states and CDN caches mask slow-burn drift and intermittent regional issues.
• Smoke-test under realistic load: replay the workflow against a test workspace for at least 30 minutes at your normal working pace, log success / error and the timestamp per attempt to a notes file.
• Capture the new state in a personal notes entry so the next time this happens you do not rediscover it. Note platform version + workspace policy + connected-apps list + failing screenshot + verbatim error string + fix applied. Push to a shared team wiki if your team uses one.
• If the fix involved an API token rotation or a workspace policy change, commit the new token to your password manager and screenshot the workspace settings for archival.

Safety, rollback, blast radius

• Test in a Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 test workspace or on a duplicate scenario first before any change that touches the real workspace. Snapshot the platform version, the workspace settings, the connected-apps list, and the sharing policy before changing anything.
• Apply the principle of least surprise when granting share access or connected-app permissions. Review the share list against the people who actually need access - extra shares are extra blast radius.
• Use idempotent runs where the Google Apps Script, Sheets Automation with SpreadsheetApp, 2026 API supports it (the platform's run id de-dupe, external id keys on destination records) so a retried run does not create duplicate records.
• Know your rollback path. Platform version rollback is a one-line download-and-install; an API token rotation is reversible if you kept the old token in the password manager during cutover; a workspace policy change is reversible only if you saved the previous policy in a screenshot.
• For team-wide or workspace-wide changes, line up a maintenance window with team notification before pushing through the admin console.

FAQ

Related fixes

Related guides worth a look while you sort this one out:

• how to detect a paste of a formula vs a value in onEdit using e.value vs e.range.getFormula
• how to detect a Sheet response edit using onEdit and FormResponse.getEditResponseUrl
• how to embed a Sheets chart into a Doc using SpreadsheetApp.getActiveSheet.getCharts and Body.insertImage
• how to detect and skip Drive shortcut files using DriveApp.File.getMimeType application/vnd.google-apps.shortcut
• how to detect duplicate submissions by email using FormResponse.getRespondentEmail and a Sheet dedupe
• how to convert formula-driven Sheet output to values with Range.copyTo CopyPasteType VALUES