Hi @Konstantin-9879 ,
Update: I have received an update from Product team on this issue. This has been identified as a bug and a hotfix has been applied to all regions.
In order to overcome the issue, please do follow the below steps:
- Clone the renamed child pipeline which is having issue and give a different name.
- Delete the renamed child pipeline (old) that is having issue.
- Go to
Settings
section of your parent (Execute) pipeline and select the newly cloned child pipeline. - Publish the changes
- Now please try firing the parent pipeline using
Trigger Now
option - Your pipelines should run with out any issue.
I have tested and verified that it is working as expected.
Hope this resolves your issue and apologies for the inconvenience caused because of this.
Please let us know if you see any further issues.
Thank you
----------
Please do consider to click on "Accept Answer" and "Upvote" on the post that helps you, as it can be beneficial to other community members.