> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/reference/operations/calendar.md).

# Calendar

The calendar shows time-based activity for your solution. It plots [service schedules](/reference/operations/schedules.md) and [flow schedules](/reference/flows/schedules.md) alongside past and scheduled [deploys](/reference/operations/deploy.md) and Appfarm platform maintenance windows on a day, week, or month grid.

The calendar is read-only. Click any entry to open a popover with its details and a button to navigate to its source.

<figure><img src="/files/i0vVO9KdsXSHiziTU7OR" alt=""><figcaption><p>The Calendar in Appfarm Create</p></figcaption></figure>

## Views

The selector in the top-right of the toolbar switches between **Day**, **Week**, and **Month**. All three views show the same items at different time resolutions.

**Today** returns the calendar to the current date. The arrow buttons step forward and back by the selected resolution.

## What appears on the calendar

Items from every [environment](/reference/configuration/environments.md) are shown together on a single calendar. There are no filters.

### Schedules

Service and flow schedules appear at the times they are configured to run, alongside a description of the schedule and the schedule's time zone.

Service schedules have their own name. The calendar entry shows the schedule name, marked with a yellow dot. Flow schedules do not have a name; the calendar entry shows the name of the [flow](/reference/flows.md) [action](/reference/actions.md) that is scheduled, marked with a blue dot. A flow action can carry multiple schedules — each appears as its own entry in the calendar.

The popover shows the schedule description, the time zone, and the parent service or flow as a link. **Go to Schedule** opens the schedule itself.

If a schedule runs more than once within an hour, a multiplier is appended to the entry — for example, `(2×)` or `(30×)` indicates 2 or 30 runs within that hour.

Disabled schedules still appear on the calendar, but are grayed out.

Schedule entries are plotted on the calendar grid using your system time zone. The time zone shown in the entry label — for example `(Europe/Oslo)` — is the schedule's own configured time zone, which is the basis for when it actually runs.

### Deploys

Both completed and scheduled deploys are shown on the calendar. Completed deploys are labeled **Deployed to** the target environment — for example, **Deployed to Test**. Scheduled deploys are labeled **Deploy to** the target environment — for example, **Deploy to Staging**. The popover shows the time of the deploy, and **Go to Deploy** opens the [Deploy](/reference/operations/deploy.md) page.

### Scheduled maintenance

Maintenance windows announced by Appfarm for the platform appear at their planned time. The popover links to the [Dashboard](/reference/dashboard.md), where details are listed.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.appfarm.io/reference/operations/calendar.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.