Issue Summary

Discovery imports are sometimes not populating referenced object attributes scanned on the same execution due to racing conditions.

It occurs when the actual object is created, however its referenced attribute objects are still not completely created by the import.

Steps to Reproduce

1. Execute a scan that should automatically send its data to cloud.

Expected Results

Referenced object attributes should be correctly populated.

Actual Results

Referenced object attributes aren't populated.

Workaround

Update your discovery scan using the None export type and upload the generated .zip file in the corresponding import on assets cloud import configuration.

After that execute the import twice.