The "Stop a Docker Resource" step shows a missing resource chip and assigns a GUID instead of a slug in the "From Steps" field when added to a CaC process

[HuyPhanNguyen]

Severity

No response

Version

Earliest try 2025.3.7427

Latest Version

I could reproduce the problem in the latest build

What happened?

The "Stop a Docker Resource" step shows a missing resource chip and assigns a GUID instead of a slug in the "From Steps" field when added to a CaC process.

Reproduction

• In a CaC deployment process, add a Run a Docker Container
• Then add a Stop a Docker Resource step. Configure the From Steps field to point to the previous Run a Docker Container step
• Commit the changes
• Note: The Stop a Docker Resource - From Steps field shows a missing resource chip.
• Note: The Stop a Docker Resource in OCL will have the From Steps field set to a GUID instead of a slug. When the process gets executed in a deployment, the containers from the Run a Docker Container step won't be stopped. The above only happens for newly added Run a Docker Container and Stop a Docker Resource steps.

Error and Stacktrace

More Information

No response

Workaround

• Commit "Run a Docker Container" step first
• Then add "Stop a Docker Resource" step it will use the slug as reference instead of GUID