From the IDP service/component view (CI/CD / executions tab):

Users can see the list of previous Harness CD pipeline executions and click Rerun, but:

Runtime input parameters cannot be modified before rerun (it blindly reuses the last inputs).

If the pipeline has no prior executions, nothing is shown and there is no way to run it from IDP at all.

As a result, users must click through to the Harness CD UI to start or parameterize a pipeline run instead of doing it directly from IDP.

Use Case (as described by Hari)

Hari wants developers to be able to:

Stay in IDP and, from the component view, trigger Harness CD pipelines directly for that service.

For an existing pipeline, start a new execution while changing runtime parameters (e.g., target environment, image tag, flags) without going to the CD UI.

For a new or never-run pipeline, initiate the first execution entirely from IDP, instead of needing a previous run in order to see anything in the executions list.

This is part of their goal to use IDP as the front door for deployments and avoid context-switching to Harness CD.