Strange (corrupted?) ADF Pipeline behaviour

I have had several instances in ADF pipeline where the pipeline behaves different from what expected during debug runs.

Setting a variable - how it should work:
I use a pipeline parameter (String: 2023-05-24T00:00:00Z) to set a variable.

When I do this in an otherwise empty pipeline1 the variable becomes 2023-05-24T00:00:00Z, what I expect.

How it work in my pipeline:

However in my other pipeline2 a similar activity with the same input, results in 2023-05-24 00:00:00, without the T and Z. The only difference being that this pipeline is being executed from a parent pipeline. 

The strangest thing is that my colleague can run the same pipeline2 and he DOES get the desired result: 2023-05-24T00:00:00Z.

Also, I can't seem to debug pipeline2 on its own, it does not seem to respond.
However, when I clone pipeline2. I can debug the cloned pipeline.

Is had the same issue with different pipelines, where cloning the pipelines seems to solve some issues. Is my pipeline corrupted. How can I tell?

Removing cookies/temp files and restarting cluster and whole computer did not work.

How to deal with this behaviour?