Background / Use Case:

Currently, there is no expression available to retrieve the sequence ID of a previous pipeline run. This creates challenges in scenarios where artifacts are tied to the pipeline’s sequence ID.

Example Use Case:

The pipeline builds an artifact and names it using the expression build-<+pipeline.sequenceId>.

The artifact is published to S3 with the key <+pipeline.sequenceId>.

Subsequent steps depend on the existence of this S3 object using the same key.

Problem:

If one of the downstream steps fails and the pipeline is rerun, the new run gets an incremented sequenceId. As a result, the steps look for an artifact at <+pipeline.sequenceId + 1>, which does not exist, causing the rerun to fail.

Request:

Add support for detecting reruns and accessing the previous pipeline’s sequence ID (e.g., <+pipeline.previousSequenceId>). This would allow reruns to reuse artifacts or outputs from the original run instead of failing due to sequence ID mismatches.