What Happens to a Territory Request If the System Goes Down?

What Happens to a Territory Request If the System Goes Down?


Info
Short answer: It still gets answered. Franchise Ninja Territory Checks include built-in auto-retry and recovery, so a territory request is never lost because of a temporary system failure. If a service behind the scenes stops responding, the request is held, retried automatically, and completed as soon as service returns. No one on your team has to resubmit anything.

Why This Matters to Your Brand

Every territory request represents a broker and a candidate waiting for an answer. When that answer stalls, interest cools and the broker may move on to a brand that responds faster.

Most of the time, Franchise Ninja returns a territory answer in about 59 seconds. But every cloud platform depends on outside services, and any of those services can slow down or go offline for a period of time. The question is not whether an outage could ever happen. The question is what happens to your requests when it does.

With Franchise Ninja, the answer is simple: the request waits, retries, and finishes.

How Auto-Recovery Works

Territory Checks are designed with failure in mind. When a check cannot be completed on the first attempt, the platform follows a recovery process instead of dropping the request.
  1. The failure is detected. The system recognizes when a service it relies on is unresponsive or taking too long to reply.
  2. The request is kept, not discarded. The territory request stays in process rather than failing silently or disappearing.
  3. The system retries automatically. Franchise Ninja keeps reattempting the check until the affected service is back online.
  4. The check is completed. Once service returns, the request is processed using your brand's territory rules, and the result is delivered just like any other check.
  5. The team is alerted. Automated alerts notify the Franchise Ninja team the moment an issue starts, so they can monitor recovery in real time.
All of this happens without user intervention. Your brokers do not need to resend the request, and your development team does not need to chase it down.

Ninjas on Watch 24/7

Automated recovery handles the work. Automated alerts make sure people are watching it.

When a recovery event begins, the Franchise Ninja team is notified right away. That means a real person knows what is happening, can track the request through to completion, and can step in if anything unusual comes up. Your territory requests are covered by both the system and the team behind it, around the clock.

What You Might Notice During an Outage

In the rare case that an outside service goes down, the main thing you may notice is time. A check that normally returns in about 59 seconds may take longer while the platform waits for service to return.

What you will not notice:
  1. A lost or missing territory request
  2. A need to resubmit the request
  3. A broker left without an answer
Even with a delay, an automated answer is still typically faster than a manual territory check routed through email, spreadsheets, and mapping lookups.

Frequently Asked Questions

Are territory requests ever lost if Franchise Ninja experiences a system failure?
No. Auto-retry and recovery are built into Territory Checks. If a check cannot be completed right away, the system keeps retrying until it can finish the request.

Do I need to do anything if a check is delayed?
No. Recovery happens automatically. There is no need to resubmit the request or contact support for the check to be completed.

How does the Franchise Ninja team know when something goes wrong?
Automated alerts notify our team as soon as a recovery event begins. The team monitors the request until it is processed.

Will a delayed check still follow my brand's territory rules?
Yes. Once the request is processed, it runs through the same brand-specific rules as every other Territory Check.

How often do outages happen?
System failures are rare. Auto-recovery exists so that when one does happen, your requests are protected.