Events

事件能够捕获流程执行过程中的事件发生时间。流程图绘制事件主要有三种类型：开始事件、中间事件和结束事件。这些事件也被称为“捕获”事件（对触发器做出反应）或“抛出”事件。

UiPath 平台支持以下事件类型和实现：

• 开始事件的行为与捕获事件相同。它们由以下因素触发：
  • 无（手动触发时启动流程或通过 Orchestrator 启动）
  • 消息事件（等待来自 Integration Service 的事件触发器）
    
    
    
    
  • 计时器事件（按触发器配置中定义的计划或延迟开始流程）

    A Timer start event begins a process based on a defined schedule rather than user or system input. You can configure it using a Timer section that supports three types: Date, Duration, or Cycle.

    For recurring executions, use the Cycle type and specify the Repeat frequency (e.g., hourly, daily) and interval. The At and Repetitions fields allow additional control over timing and limits.

    In the Implementation section, the Action can be set to None if no inbound event is needed, or Wait for connector event if the process should also listen for an external trigger before proceeding. Timer start events are ideal for scheduled automations such as hourly syncs or daily reports. Read more about Integration Services connectors.

    
    
    
    
    
• 中间捕获事件的行为与开始事件类似。它们在流程执行期间等待消息、计时器或 API 触发器。执行暂停，直到收到消息。
• 边界事件是附加到任务的特殊类型中间捕获事件。它们可以配置为：
  • 中断性边界事件：当附加任务开始时，边界事件会等待其触发器。如果任务仍在执行时被触发，它会中断任务并沿边界事件输出路径继续运行。中断性边界事件可以通过“计时器”或“消息”事件触发。

    A timer boundary event allows you to interrupt a task if it takes too long to complete. You can configure the timeout using either a Duration, a specific Date, or a Cycle (for recurring timers).

    In the properties panel, the Type field determines the timer mode, and the Value field accepts ISO 8601 time expressions (e.g., PT1H for one hour). If the timer expires while the task is still running, the process continues along the boundary event’s outgoing path.
    The Implementation section lets you optionally define actions to take when the timeout is triggered, though it's commonly left as None if the follow-up logic is modeled downstream.
    

    

    
    

    A message boundary event listens for a specific message while the activity it’s attached to is still running. If the message arrives, it interrupts the ongoing task and diverts the flow to a separate path.

    You can define the message handling logic in the Implementation section by selecting an available action (e.g., wait for connector event or external input). Use the Inputs and Outputs sections to pass or extract data from the incoming message. You can also use Update variables to modify process data in response to the message. If no message is received, the original task continues uninterrupted.
    

    

    
    
  • 非中断性边界事件：触发时，这些事件会创建新的执行令牌并沿并行路径继续运行，而不会中断原始任务的执行。非中断性边界事件可以通过“计时器”和“消息”事件触发。
  • Error boundary events: An Error boundary event is used to catch and handle errors that occur in the activity it is attached to. If an error is thrown, control exits the activity and flows down the boundary event path. By default, the Exception is set to Catch all, which means it captures any unhandled error. In most cases, this path acts as a fallback or "ultimate" error-handling route.
  • The Implementation section allows you to optionally define actions (such as logging or notifying), but it can be left as None if no specific execution is required within the boundary event.
    
    
    
    
• 中间抛出事件主动发送触发器。例如：
  • 消息中间抛出事件的作用类似于“发送任务”，会调用 Integration Service API 执行。
• 结束事件标志着流程的完成，行为与抛出事件相同。此类事件可能是：
  • 错误结束事件，完成流程实例并导致 orchestration runtime (OR) 作业出现故障。
  • Message end events, which send a message as the process concludes. A Message end event can be configured to execute a connector activity when the process reaches its end.

    By selecting "Execute connector activity" as the implementation action, you can trigger an outbound operation using any connector available in Integration Service—such as Slack, Salesforce, ServiceNow, or others. This is commonly used to notify external systems, update records, send messages, or upload files upon successful or failed process completion. You must select the target Connector, define the Connection, and choose the specific Activity to run. Inputs allow you to pass data to the connector, while Outputs let you capture and store the connector’s response or result for use elsewhere in the process. Read more about Integration Services connectors

    。
    
    
    
    
  • Terminate end event, which cancels all other execution paths/tokens, especially when multiple branches run in parallel. An End event signifies the conclusion of a process path.

    In Maestro, you can optionally define an Implementation action to perform a final activity—such as executing a connector operation, returning data, or triggering a follow-up system. If no action is needed, the implementation can be set to None, which simply ends the process flow.

    The Arguments section allows you to define output values that can be passed to parent processes or used in downstream reporting. End events are flexible and can be used to close both standard and exceptional paths, depending on how the process is modeled.