Skip to content

fix: use destination definition name in place of string for custom object #6742

fix: use destination definition name in place of string for custom object

fix: use destination definition name in place of string for custom object #6742

Annotations

10 warnings

This job succeeded