This article helps to explain how SD-Cloud is designed to handle Shared objects like Addresses, services etc.

Current behavior in SDC is -> an object say ABC has values 123 and in use in a particular FW policy..

• Then if you try to import another FW policy, if that also has ABC object but with value say 1234, then it will create another object like ABC_1 in SDC..
• Otherwise, there is option to override with imported values where current SDC object will be changed and value 1234 will be assigned.
• In Old legacy SD or even in SD-Cloud, current behavior has been always like treating an object as global resource to be available for all Devices/policies managed by the SDC/SD.

We had a similar bug reported by our internal teams to Juniper SDC cloud Engg team where import gets stuck or hunged with large number of objects in the Firewall/SRX..

• The current solution from Engg was to get rid of UnUsed Objects and Duplicate objects -> Delete them and try import again..
• Also, the future plans for upcoming release is to enhance the Object management and allow more number of Object handling by SDC.. so may be in future you will see better Object management by SDC ..

But for now, this is as per the current design limitation.

 Please contact JTAC for any queries or support.