Skip to main content

Catching Silent ArcGIS Service Failures with a Lightweight Chrome Extension

· 3 min read
Mayro Najarro

Introducing Quetzly Validator for Chrome an Extension for ArcGIS Service Validation​

ArcGIS services can fail in ways that aren’t immediately obvious. A service might load fine in the REST directory, report a healthy status, and look normal at first glance — yet still return unexpected errors, missing fields, or incomplete data when an application tries to use it.

These kinds of silent failures are some of the hardest to catch. And in many cases, the first sign of trouble is a user reporting that a map isn’t loading. I wanted a faster, simpler way to validate services before issues reached users something lightweight enough to use during development, troubleshooting, or quick checks throughout the day. That’s what led me to build the Quetzly Chrome Extension.

Why a Chrome Extension?​

There are plenty of ways to test ArcGIS services, but most of them require setup, scripting, or switching tools. I wanted something that:

  • works directly in the browser
  • requires no installation beyond Chrome
  • is available the moment you need it
  • encourages quick, proactive checks
  • fits naturally into everyday GIS workflows

The goal wasn’t to replace existing tools — just to make validation easier and more accessible.

What the Extension Does​

The extension runs a small set of checks against an ArcGIS service and highlights anything that doesn’t match what you expect. It currently validates:

  • Layer count
  • Spatial reference
  • Attribute schema
  • Basic export test
  • Expected vs. actual values

If something looks off, the extension flags it immediately. It’s intentionally simple with no configuration files and no setup. Just quick validation from the browser.

When It’s Most Useful​

I’ve found the extension especially helpful for:

  • verifying services right after publishing
  • catching unexpected schema changes
  • confirming a service is returning data before integrating it into an app
  • troubleshooting user‑reported issues
  • validating services during development

It’s designed for speed and convenience — the kind of tool you use multiple times a day without thinking about it.

A Note on the Desktop Version​

For batch validation or scheduled checks, I also built a desktop version of the validator. It’s useful when you need to test multiple services at once. But for quick, everyday validation, the Chrome extension is the fastest and simplest option. It's also a great option for those who are not allowed to install chrome extensions on their work computers.

Try the Extension & Leave a Review​

If you’d like to try the Chrome extension, you can download it directly from the Quetzly Chrome Web Store Page. It’s free to use, and early feedback is incredibly helpful at this stage.

If you find it useful, leaving a quick review in the Chrome Store makes a big difference. It helps others discover the tool and gives me a better sense of what’s working and what needs improvement.

Thank you to anyone who takes a moment to try it out. Your feedback really does shape where this tool goes next.