dsanderbi opened a new issue, #5484:
URL: https://github.com/apache/hop/issues/5484
### Apache Hop version?
2.14
### Java version?
17
### Operating system
Windows
### What happened?
According to the Apache Hop documentation, **${Internal.Pipeline.ID}** is
supposed to represent:
> "The unique ID of the current pipeline execution. This ID is useful for
referencing and tracking execution instances in logs or external systems."
This implies that each time a pipeline is executed, a **new unique ID**
should be assigned to **${Internal.Pipeline.ID}**.
However, in practice, I’ve observed that **${Internal.Pipeline.ID}** remains
the same across multiple executions of the same pipeline.
In contrast, **${Internal.Workflow.ID}** behaves as expected — it is
re-generated and unique for every workflow execution.
# Pipeline
# Workflow
# File
[pipeline_id.zip](https://github.com/user-attachments/files/21051409/pipeline_id.zip)
### Issue Priority
Priority: 2
### Issue Component
Component: Hop Gui, Component: Pipelines
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
