- Release Notes
- Overview
- Uploading data to Communications Mining™
- Using the Dispatcher Framework
- Activities reference
- Get Stream Results
- Get Attachment
- Create Communications Mining Validation Action
- Create Communications Mining Validation Artifacts
- Create Record
- Get Record
- Fetch Batch from Stream (Legacy)
- Advance Stream
- Reset Stream
- Retrieve Communications Mining Validation Artifacts
- Predict Record(s)
- Wait For Communications Mining Validation Action
- How-to guides
Communications Mining activities
UiPath.CommunicationsMining.Activities.Streams.AdvanceStream
Table 1. Advance a given stream
| Name | Direction | Description | Is required |
|---|---|---|---|
| Select the stream to advance | Input | Select the stream that is an output of the Fetch Batch from Stream activity | True |
| Advance to the latest Sequence ID | Input | Advance the selected stream to the last fetched record’s ID | True |
| Advance to | Input | Sequence ID you received from the Fetch Batch from Stream activity | True |
| Advance stream response | Output | Advance stream response | False |
Choosing how to advance the stream
The Advance to the latest Sequence ID toggle controls whether the stream advances the entire batch at once or per individual record.
-
Enabled — Advances the entire batch to the last fetched record’s ID in a single operation. Use this option only if your automation can handle receiving the same messages more than once — for example, if you have de-duplication logic in place. If the process fails midway through a batch and restarts, any already-processed messages that were not yet advanced will be returned from the stream again.
-
Disabled (default) — Use the
in_AdvanceToSequenceIdargument to advance the stream per individual record processed. This is the default behavior in the Dispatcher framework and is the safer option when your automation does not handle duplicates.