> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/tutorials/components/calendar/troubleshoot-resources-and-missing-events.md).

# Troubleshoot resources and missing events

Find out why the Avonni Calendar shows an Empty row or leaves events out, check mappings, dates, time zone and hours, and hide unassigned events.

A dispatcher opens the team calendar and sees a row labelled **Empty** above the technicians, or a visit they know exists is not on the board. Both come from the same few settings: how events are tied to resources, which dates and hours the calendar shows, and the time zone it reads them in.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FRc2XkHNE3YyRRrybYvYE%2Fcalendar-troubleshoot-resources-and-missing-events-result.png?alt=media" alt="Team calendar week with a row labelled Empty above three technicians, holding Leak check on Monday and Warranty repair on Tuesday"><figcaption><p>Visits with no technician land on the Empty row.</p></figcaption></figure>

## Before you start

* You have a working calendar, built with the [Calendar 101](/flow/tutorials/components/calendar/calendar-101-tutorial.md) (Variable) or [Use a Query data source](/flow/tutorials/components/calendar/using-a-query-data-source.md) (Query).
* Have one missing visit in mind, with its technician, date and time. Checking one known record is faster than checking them all.

## Steps

{% stepper %}
{% step %}

### Check how events are tied to resources

The calendar places each event on the row whose resource matches the event's **Resource Name**.

* **Variable**: the value in the event's **Resource Name** must equal the resource **Key Field**. If events hold a User ID, the resources must use User ID as **Key Field**. An event whose value matches no resource is not shown at all.
* **Query**: **Resource Name** must be a lookup to the record that should be a row, for example a **Technician** lookup to User. If **Resource Name** is empty, every event goes under one resource.
* In both modes, an event with no value in **Resource Name** goes on the **Empty** row.
  {% endstep %}

{% step %}

### Check the dates the calendar opens on

* **Start Date** sets where the calendar opens. Empty means today. A mapped date variable that is not set yet also falls back to today.
* The visible range follows **Selected Time Span**: a visit next Tuesday is not on a **Day** view of today. Move forward with the toolbar, or open on **Week**.
* **From** and **To** must both be mapped. Map them to date-time fields (`StartDateTime`, `EndDateTime`) for timed visits, or map **All Day** for all-day events.
  {% endstep %}

{% step %}

### Check the time zone

The calendar shows times in the time zone of the running user's Salesforce settings, not the computer's. A visit saved at 09:00 New York time shows at 15:00 for a dispatcher whose Salesforce time zone is Paris.

Turn on **Show Time Zone** to let the end user see the time zone in use and switch to another one.
{% endstep %}

{% step %}

### Check the hours and days the calendar draws

Under **Available Times**, the calendar only draws the periods you allow:

* **Time Frames**: an event at 19:00 has no slot if the frame is `08:00-18:00`.
* **Days**: weekend visits do not show if only Monday to Friday is allowed.
* **Months**: the same rule, for months.

Widen the frame, or move the event. [Block past dates and limit working hours](/flow/tutorials/components/calendar/block-past-dates-and-limit-working-hours.md) covers these settings.
{% endstep %}

{% step %}

### Decide what to do with events that have no resource

An **Empty** row is the calendar's place for unassigned events. A dispatcher often wants it, to see what still needs a technician. If you do not:

1. In the **Event Display** group, turn on **Hide Empty Resource Events**.
2. Events with no resource disappear, and so does the **Empty** row.

{% hint style="info" %}
Events from an ICS calendar or a Content Document belong to no resource and are never hidden. While **ICS Calendar links or Content Document IDs** is filled, the **Empty** row stays. See [Show an Outlook or Google calendar with ICS links](/flow/tutorials/components/calendar/show-an-outlook-or-google-calendar-with-ics-links.md).
{% endhint %}
{% endstep %}

{% step %}

### Save and test

Save the flow and run it with **Debug** on the week of your missing visit. It now sits on its technician's row at the time you expect. Unassigned visits sit on the **Empty** row, or are gone if **Hide Empty Resource Events** is on.
{% endstep %}
{% endstepper %}

## Troubleshooting

<details>

<summary>An Empty row appears above the technicians</summary>

At least one event has no value in **Resource Name**. In Query mode, check the records where the **Technician** lookup is blank. Assign them, or turn on **Hide Empty Resource Events** if unassigned work should not show.

</details>

<details>

<summary>Every event is on one row</summary>

In Query mode, **Resource Name** is not mapped, so all events are drawn under the same resource. Map it to the lookup that holds the technician.

</details>

<details>

<summary>One Empty row and no events at all, in Query mode</summary>

**Resource Name** is mapped to **Assigned To** (`OwnerId`). The screen shows no error: only the browser console reads "Error executing the resources query: sObject type 'PolymorphicReference' is not supported". That field can point to a user or a queue, and the calendar cannot build rows from it. Add a lookup to User on `Event`, fill it, and map **Resource Name** to it.

</details>

<details>

<summary>One technician's visits are missing, the others show</summary>

In Variable mode, that technician's events carry a value that matches no resource **Key Field**. Compare the value in the event's **Resource Name** field with the technician's **Key Field** value. Also check that the technician is in the resource collection: a Get Records filter can leave them out.

</details>

<details>

<summary>Visits show on a quiet week but some are missing on a busy one</summary>

In Query mode, **Maximum Number of Records** caps the number of events loaded. Raise it, or narrow the **Filters** to the period on screen.

</details>

<details>

<summary>A visit shows a few hours off</summary>

The running user's Salesforce time zone differs from the one the visit was planned in. Check the user's time zone in their personal settings, or turn on **Show Time Zone** so the end user can see and change the zone in use.

</details>

## Related tutorials

* [Calendar 101](/flow/tutorials/components/calendar/calendar-101-tutorial.md): the resource and event mappings for a Variable data source.
* [Use a Query data source](/flow/tutorials/components/calendar/using-a-query-data-source.md): rows from a Technician lookup.
* [Filter and search a team calendar](/flow/tutorials/components/calendar/filter-and-search-a-team-calendar.md): when a technician is hidden by the resource filter.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avonnicomponents.com/flow/tutorials/components/calendar/troubleshoot-resources-and-missing-events.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
