Whenever we duplicate a service in a project, the target service gets created without the sealed variables from the original service.

When we then manually re-create the sealed variable (still during the setup stage of the duplicated service, before it's been created), presumably due to some kind of bug, the service ends up being created with an empty value for that sealed variable.

Because of how sealed variables work, you can't view them after they're saved.

It's hard to notice this until production breaks later due to the missing variable, even though we entered the value correctly in the UI on our end.

This has already broken production for us twice, and it's very difficult to catch before issues arise.

Could this be fixed? Either by allowing sealed variables to carry over to duplicated services, or by fixing the bug that prevents them from being saved during service duplication?