> For the complete documentation index, see [llms.txt](https://bpmflow.gitbook.io/project/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bpmflow.gitbook.io/project/functional-and-technical-information/timers/timers-and-calendars.md).

# Timers and Caledars

The default behavior for **Event Timer** is to count time sequentially. However in the real world this is not the case, for example, sundays maybe does not count in a due date and hours can be applicable when an office is open. **Event Timer** can used in combination of **Bpm Calendars**. The **Timer** will use the **Calendar** if particular day or hour should be taken into account when a due date is calculated.

Check calendars at: [Calendars in Bpm Flow](/project/application-manuals/backoffice-manual/main-menu/applications/manage-calendars.md)

![](https://3974112602-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LH4gGgyMb1_fhOg782r%2F-LHEeWu6oIweMna7rFHs%2F-LHEePt2VoNRXGkETEjn%2Ftimer-calendar-code.jpg?alt=media\&token=a70dce7b-06df-4f1a-be45-fdf50a03a5a4)

In the example above the timer will be activated if the \[***lastExecutionTime***] plus \[***termValue***] is less than current time. In this case \[***termValue***] was defined in a previous step in the process. Also the calculation of days is bound a **calendar** named \[***Default***]. This calendar for example can have Sundays and Saturdays disbable.

Note: **Bpm Flow** can have N defined calendars.