Camunda Timer Events Explained: Complete Guide with BPMN Examples
Camunda Timer Events Explained: Complete Guide with BPMN Examples
In workflow automation, processes often need to wait for a specific time or trigger actions based on schedules.
For example:
Send reminder email after 24 hours
Escalate a task if not completed within 2 days
Run a process every night at midnight
In Camunda BPM, these scenarios are implemented using BPMN Timer Events.
Timer events allow processes to pause execution until a defined time or duration occurs.
In this guide we will cover:
What Camunda timer events are
Types of timer events in BPMN
Real workflow examples
Timer configuration options
Best practices for workflow designers
What is a Timer Event in Camunda?
A Timer Event in BPMN is used to trigger process execution based on time conditions.
Instead of triggering a workflow manually, the process waits for:
a specific date
a time duration
a recurring schedule
Camunda supports these timer definitions using ISO-8601 time formats or cron expressions.
Example scenarios:
| Scenario | Timer Example |
|---|---|
| Reminder after delay | 24 hours |
| Escalation | after 2 days |
| Scheduled workflow | every night |
Timer events help automate time-based business logic.
Types of Timer Events in Camunda
Camunda supports three main types of timer events.
1️⃣ Timer Start Event
A Timer Start Event automatically starts a process at a specific time or schedule.
Example:
Run workflow every day at midnight
Generate report every week
Example BPMN configuration:
0 0 0 * * ?
This cron expression triggers the process daily at midnight.
2️⃣ Intermediate Timer Event
An Intermediate Timer Event pauses the process for a defined duration.
Example:
Customer submits request
Process waits 48 hours
Send reminder notification
Example configuration:
PT48H
This means wait for 48 hours.
3️⃣ Boundary Timer Event
A Boundary Timer Event is attached to a task and triggers an alternative flow if the task takes too long.
Example scenario:
Task: Manager Approval
Timer: 2 days
If the manager does not approve within 2 days, the workflow escalates.
Example BPMN design:
Manager Approval Task
|
|--- Boundary Timer Event (2 days)
|
→ Escalate Task
This pattern is commonly used for SLA management.
Timer Configuration in Camunda
Camunda supports three timer definition formats.
| Timer Type | Example | Description |
|---|---|---|
| Date | 2026-03-15T10:00:00 | Trigger at specific time |
| Duration | PT24H | Trigger after 24 hours |
| Cycle | R/PT10M | Repeat every 10 minutes |
Examples:
Duration
PT24H
Waits 24 hours.
Cycle
R5/PT1H
Repeats 5 times every hour.
Cron
0 0 12 * * ?
Runs process daily at 12 PM.
Example: Customer Support Escalation Workflow
Let’s consider a customer support workflow.
Process:
Customer creates support ticket
Agent reviews ticket
Manager approval required
If the manager does not respond within 24 hours, the ticket is escalated.
This can be implemented with a Boundary Timer Event attached to the approval task.
Workflow behavior:
Customer Ticket
↓
Agent Review
↓
Manager Approval
↓
Boundary Timer (24h)
↓
Escalate Ticket
This ensures service-level agreements (SLAs) are respected.
Common Use Cases for Timer Events
Timer events are widely used in workflow automation.
Examples include:
Task reminders
Escalation workflows
Scheduled reports
Subscription renewals
Order processing delays
They are especially useful for long-running processes.
Best Practices for Camunda Timer Events
When designing BPMN workflows, follow these practices.
Use boundary timers for SLAs
Examples:
approval deadlines
ticket escalation
overdue notifications
Avoid excessive timers
Too many timers may impact process performance.
Use timers only when time-based logic is required.
Use cron carefully
Cron expressions must be accurate and tested to avoid unexpected workflow triggers.
Recommended Articles
If you work with Camunda, BPMN, or Java enterprise architecture, you may also find these guides helpful.
BPMN Compensation Events Guide
Learn how to reverse previously completed actions in a BPMN workflow using compensation events.
https://shikhanirankari.blogspot.com/2026/03/bpmn-compensation-events-guide-when-and.html
Liferay vs Spring Boot – When to Use Which
A comparison between an enterprise portal platform and a Java backend framework, including real-world architecture scenarios.
https://shikhanirankari.blogspot.com/2026/03/liferay-vs-spring-boot-when-to-use-which.html
Final Thoughts
Timer Events are one of the most powerful features in Camunda BPMN workflows.
They allow processes to:
trigger automatically
wait for specific durations
escalate delayed tasks
For developers building workflow automation systems with Camunda, understanding timer events is essential for designing robust and reliable business processes.
Recommendation for Workflow Architects
Use timer events when:
✔ workflows require scheduled execution
✔ tasks must follow SLA deadlines
✔ business processes involve waiting periods
Avoid using them when:
❌ timing logic is unnecessary
❌ process complexity increases without business value
Proper use of timer events can significantly improve process automation and reliabilit
Comments
Post a Comment