maestro
latest
false
UiPath logo, featuring letters U and I in white

Maestro user guide

Last updated Dec 12, 2025

Time and reminders

Reminder attached to a task (non‑interrupting timer)

A user task with a repeating non‑interrupting timer that triggers reminders.

Use when

  • You want periodic reminders while a task stays open.
  • The task should remain available until completion or timeout.

Pattern in simple words

  1. Start.

  2. User task: Await submission. Attach a non‑interrupting boundary timer set to a schedule, for example every three days.

  3. On timer: Service task Send reminder. End Reminder sent.

  4. Main path: Exclusive gateway Submitted? If Yes, End Graded. If No and deadline reached, End Deadline missed.

    Note:

    The timer does not stop the user task.

    Other scenarios

  • Finance: Invoice approval reminders.
  • Healthcare: Appointment reminders before due date.
  • Manufacturing: Supplier update reminders.
  • Retail: Purchase order follow‑ups.
  • Public sector: Application completion reminders.

Deadline breach stops the task (interrupting timer)

A user task that either completes on message or is terminated by a timer.

Use when

  • A task must end automatically after a fixed duration.
  • There is a clear SLA or cutoff.

Pattern in simple words

  1. Start.

  2. User task: Await confirmation. Attach an interrupting boundary timer set to a duration, for example 48 hours.

  3. On timer: Service task Cancel booking. End Cancelled.

  4. On message Confirmation received: Service task Schedule install. End Scheduled.

    Note:

    The interrupting timer ends the user task when time expires.

    Other scenarios

  • Finance: Month‑end approval deadline triggers escalation.
  • Healthcare: Consent not received by deadline leads to reschedule.
  • Retail: Quote expiration triggers closure.
  • Public sector: Unanswered notice triggers auto‑closure.
  • Manufacturing: Unacknowledged purchase order triggers auto‑cancel.

Start on a schedule (timer start)

A process that begins with a timer start and runs a service task on a schedule.

Use when

  • The process must start on a recurring schedule.
  • Execution is independent of external input.

Pattern in simple words

  1. Timer start: Every day at a specific time, for example 05:00.

  2. Service task: Optimize routes.

  3. End Routes ready.

    Note:

    Define the recurrence schedule and timezone.

    Other scenarios

  • Finance: Daily cash‑flow report.
  • Healthcare: Daily patient census updates.
  • Retail: Nightly inventory sync.
  • Manufacturing: Daily production scheduling.
  • Public sector: Nightly data consolidation.

Staged escalation (laddered timers)

A user task with two non‑interrupting timers for reminders and a final interrupting timer for closure.

Use when

  • You want multiple reminders before a final close.
  • Work continues until the final condition or message arrives.

Pattern in simple words

  1. Start.

  2. User task: Await required documents.

  3. Non‑interrupting timer after three days: Service task Send gentle reminder. End Reminder one sent.

  4. Non‑interrupting timer after seven days: Service task Send urgent reminder. End Reminder two sent.

  5. Interrupting timer after ten days total: Service task Close case for no response. End Closed.

  6. Interrupting message Documents received: User task Review submission. End Reviewed.

    Note:

    Use non‑interrupting timers for reminders and one interrupting control for closure.

    Other scenarios

  • Finance: Expense receipts overdue — reminder, warning, close.
  • Healthcare: Missing pre‑op clearance — reminder, escalate, reschedule.
  • Manufacturing: Vendor compliance documents — staged reminders before cutoff.
  • Retail: Supplier purchase order confirmation — staged follow‑ups.
  • Public sector: Missing grant application forms — staged reminders.

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo
Trust and Security
© 2005-2025 UiPath. All rights reserved.