When orphan management is configured to move an item to a different project in Rally, Rally may return the error "Could not read: Object not found for Object ID: null" and the orphan process fails.
Logs show:
ERROR YYYY-MM-dd hh:mm:ss,zzz [-nnnnnnnnnnn | logPrefix | nnn | nnnnn | {groupName}][(orphan-flows) thread #nn - JmsConsumer[processOrphanQ]] com.go2group.connectall.adapter.rally.base.RallyBaseAdapter: [Could not read: Object not found for Object ID: null]
The orphan configuration in the database may contain a text value for the project value instead of a numeric project object ID. Rally requires an object ID reference and cannot use a text value as project names in Rally do not need to be unique.
If the installation is an on-premise install, this can be validated by increasing log level to DEBUG and looking for a line as follows:
DEBUG YYYY-MM-dd hh:mm:ss,zzz [-nnnnnnnnnn | logPrefix | nnn | nnnnn | {groupName}][(orphan-flows) thread #nn - JmsConsumer[processOrphanQ]] com.go2group.connectall.adapter.rally.base.helper.RallyEntityToJsonSerializer: Returning JSON, {"HierarchicalRequirement": {
"Project": "/project/Project Name",
"project": "Project Name"
}}
Note: If this is a SaaS instance, you may request that product support validate this on your behalf via a support ticket