No route result appears
No separate route, path line, or travel information is visible in the context being reviewed.
Limit : This absence proves neither an engine outage nor the presence of one specific missing item of data.
Help Centre · Field operations
Why was a route not generated?
A missing route does not automatically prove an outage or a single cause. This page helps you reread the result, context, appointments, and available information before another attempt or a support request. Functions, fields, and constraints may vary by flow.
Distinguish a missing route from an already identified cause
No route result automatically reveals the cause. A displayed message, a missing route, and a partial route are distinct symptoms. Reread the page, date, day, filter, or visible context, then identify the relevant appointments and available address information. A recognized address does not guarantee that a route will be produced. A missing route proves neither a coverage refusal nor a lack of availability, and sequence optimization follows a separate diagnostic. A correction or another attempt does not guarantee that a result will appear.
Observed result
Clarify what actually appears
Start by naming the symptom without immediately assigning it a technical or operational cause.
A message or warning appears
A label, status, or warning related to route calculation or display is visible.
Limit : Preserve the exact message, but do not assume it reveals the entire business or technical cause.
The route appears but seems incomplete
A result is visible, but some expected appointments, points, or segments do not appear to be represented.
Limit : A missing element proves neither its definitive exclusion nor a coverage issue.
Selected context
Reread the page, date, and visible filters
Review only the elements present in your flow and relevant to the observed result.
- The page or module used.
- The selected date, day, or period.
- The displayed filter, employee, team, or resource when they exist.
- The list of visible appointments and the current order when presented.
- Changes made immediately before the result.
- The exact message, status, or absence observed.
Limit : The presence, name, and role of these elements may vary by flow and permissions. No universal filter, role, assignment, or starting point is guaranteed.
Available information
Check five categories without inventing universal prerequisites
Reread visible or documented data without assuming that all of it is required in every flow.
Relevant appointments
Identify the visible appointments that should be represented in the context being reviewed.
Limit : Their visibility does not guarantee their inclusion under the same rules.
Address or location
Reread the selected or recognized address, or the address associated with location information, when one exists.
Limit : A recognized address guarantees neither route generation nor complete data accuracy.
Time and period
Review AM, PM, or evening periods, fixed start times, and durations when visible.
Limit : Their presence and effect may vary.
Assignment or resource
Reread the displayed employee, team, resource, or assignment when relevant and available.
Limit : No assignment, team, or mandatory starting point is guaranteed everywhere.
Message and timing of the result
Record the exact wording, where it appears, and the action that precedes it.
Limit : The message does not always identify the exact cause or mechanism used.
Distinct concepts
Distinguish route, availability, and optimization
These results are related in some operations, but they do not answer the same question.
Route
A route result or travel information presented from the available usable data when this function produces a result.
Limit : The route certifies neither distance, duration, nor future conditions.
Availability
A period or time offered in the booking flow when availability can be calculated and displayed.
Limit : A lack of availability does not automatically mean a route failed, and vice versa.
Optimization
An order comparison or proposal when this function is available.
Limit : The absence of an optimized sequence proves neither the absence of a basic route nor an outage.
Verification flow
From observed result to the next step
Proceed one step at a time to preserve an interpretable context.
Observed result
The user distinguishes a complete absence, a displayed message, and an incomplete route.
Limit : The symptom does not automatically reveal the exact cause.
Page, date, and filter reread
The context actually selected is checked.
Limit : Visible filters, roles, and information may vary.
Relevant appointments identified
The appointments expected in the result are identified without adding unnecessary personal data.
Limit : Their visibility does not guarantee their inclusion in every calculation.
Addresses and available data reviewed
Available address, time, period, or assignment information is reread.
Limit : No universal list of mandatory data should be inferred.
Message or absence documented
The exact wording, page, step, and result are recorded.
Limit : The absence of a message does not allow you to conclude that there is a silent outage.
Authorized retry or support prepared
After an authorized correction, another attempt may be made if that action is available; otherwise, the context is prepared for support.
Limit : A correction or another attempt does not guarantee route generation.
Cautious diagnostic
Review a missing or incomplete route
Avoid changing several data points at once so the result can still be interpreted.
- Identify the exact page, date, and context.
- Distinguish a complete absence, a displayed message, or an incomplete result.
- Record the exact wording and the action that precedes the result.
- Identify the relevant appointments in the visible list.
- Reread the available addresses or location information.
- Review times, periods, assignments, or filters only when visible and relevant.
- After an authorized correction, reread the context before using an available retry action.
- Prepare a support request if the result remains unexplained.
Warning : Do not change several appointments, addresses, assignments, or constraints at the same time solely to make a route appear. Multiple changes make the result harder to interpret and may affect the schedule.
Before trying again
Check before another attempt
Another attempt should remain limited, authorized, and followed by a rereading of the result.
- Use only an authorized context and actions.
- Reread the page, date, and filter.
- Avoid repeating the same action several times.
- Do not change several data points simultaneously.
- Reread the result after each authorized correction.
- Preserve the exact message or absence.
- Record the date, time, and time zone.
- Prepare a sanitized screenshot if useful.
Note : An authorized correction may modify the data or schedule. Another attempt may also refresh the displayed result. No universal simulation mode is guaranteed.
Guardrails
What this article does not guarantee
The guide helps document a result without assigning a single cause or promising an automatic correction.
- A single cause for the missing route or an automatically identified outage.
- The same mandatory data in every flow.
- An address always recognized or usable, or a map point always visible.
- That one problematic address always blocks the entire route or that an appointment is automatically excluded.
- An employee, team, assignment, or starting point always required.
- A universal provider, technical mechanism, manual override, or offline mode.
- A message revealing the entire cause or a route generated after a correction.
- A definitive distance or duration, future traffic conditions, or a certain arrival time.
- That a missing route means outside coverage or no availability.
- That optimization will be proposed.
- A reduction in kilometres or an improvement in punctuality, margin, billable time, or revenue.
Related resources
Continue with the right diagnostic
Choose the guide matching the observed result rather than automatically inferring a cause.
Territories and routes
Choose the appropriate guide to review an address, fee, route, or optimization.
View the collection →Why is an address identified as outside the service area?
Review an unrecognized address or a coverage-related result.
Read the guide →How are travel fees calculated?
Reread the applicable business rule when a fee is involved.
Read the guide →What does it mean to “optimize” a route?
Distinguish a calculated sequence from the final operational decision.
Read the guide →Route optimization
Learn how sequences may be compared, adjusted, and applied according to the data, constraints, and available actions.
View the page →Why is no availability offered?
Review possible reasons for a flow with no offered period.
Read the guide →What data may MapMyStaff process?
Learn about the categories of information that may be involved depending on the functions used.
Read the guide →How do you prepare an effective support request?
Gather useful steps and results before contacting support.
Read the guide →Help Centre
Browse the other available collections and guides.
Visit the Help Centre →Support
Contact supportDocument a missing or incomplete route
Please provide only:
- the page and flow;
- the selected date, day, or context;
- the exact absence, message, or incomplete result;
- the relevant appointments without unnecessary personal data;
- the partially masked addresses;
- the visible filter, assignment, or resource when relevant;
- the visible periods or fixed times;
- the action or correction attempted;
- the result after that action;
- the approximate date, time, and time zone;
- a sanitized screenshot if useful.
Security instruction : Never send a password, authentication code, key, token, technical secret, unnecessary full address, customer name, unnecessary personal information, or unnecessary detailed information about an employee’s movements.