Version history
By clicking the Version history button 
Deployed and Scheduled markers
When a version of a stream is deployed, the version of the stream will be marked as Deployed.
When the deployed stream is scheduled, the deployed version of the stream that is scheduled will be marked as Scheduled.
Note!
When starting a stream that is scheduled, the tagged version that is marked with as Scheduled will be the one that runs.
Autosaved version
When a stream is first created or imported, the Version history panel will show an Autosaved tag for the stream.
The Autosaved tag will be updated every time the stream is updated. There will never be more than one Autosaved tag per stream and it will reflect the latest update. Once a version tag is applied, the Autosaved tag will disappear until the next time updates are made.
Note!
Renaming the stream does not count as an update.
If updates are made, an Autosaved tag will appear above the last tagged version until a tag is applied. See Tagging versions for more information on tagging.
When looking at Stream logs, Usage audit, or Stream audit, both Autosaved versions and tagged versions will be visible, see Viewing tags.
Note!
You cannot schedule an Autosaved stream.
Maximum limit of tagged versions
You can only have 100 tagged versions of a stream. No new tagged version can be created once the limit has been reached, and previous versions will need to be deleted.
Additional actions on a stream
You can perform actions on a tagged version of a stream by clicking the More 
Button | Description |
|---|---|
View | View the tagged version of stream. See Viewing tagged versions for more information on viewing tagged versions. |
Export | Export the tagged version stream. See Exporting tagged versions for more information on exporting tagged versions. |
Deploy | Deploy the tagged version of the stream. See Deploying a stream or stream group | Deploying from the version history for more information on deploying the tagged version. |
Restore | Restore the tagged version of the stream. See Restoring tagged versions for more information on restoring tagged versions. |
Delete | Delete the tagged version of the stream. See Deleting tagged versions for more information on deleting tagged versions. |
Note!
There is only a single version of stream state, even if a stream configuration can have many versions. Therefore, be careful when modifying stateful functions like Aggregation and Deduplicate between versions.
For Aggregation, if you change the group by fields or session content/calculations between versions, you may get multiple versions of records output from the aggregation function.
For Deduplicate, if you change the checking fields between versions, this will have the same de facto effect as clearing the deduplication state (any old state will not be found by the new stream version).
How API imports appear in Version history
In the stream’s Version history, versions imported via API are shown under the Application access name that performed the import, rather than a user’s email address. This lets you distinguish between versions imported by a user in the UI and versions imported by an application.