Hi,
This does indeed look like a product issue (that is already fixed in v11). You can import the config by master data.
For reference the customization package in v10.2x for Automation Task Libraries was a bit caught up on a transition phase. In order to generate it you have to do.
cmf new iot
Then in the IoT.Package run:
yo @criticalmanufacturing/iot:tasksLibrary
You require the iot generator so if there’s any issue just run npm i @criticalmanufacturing/generator-iot --save-dev
Then inside the src/
npx yo @criticalmanufacturing/iot:task
Now you are able to run the normal cmf build and cmf pack. In the cmf pack the manifest.xml will now have as an example:
<steps>
<step type="IoTAutomationTaskLibrariesSync" content="@criticalmanufacturing/connect-iot-controller-engine-custom-tasks@1.0.0" />
In the deployment process it will grab this reference and after deploying the iot packages it will sync the ATLs. If the config is missing it won’t be able to run the integration entry that triggers the sync.

