Just to add to this: It's worth checking the 'DocumentForeignKeyValue' value in the CMS_Document table.
We had this exact issue and the cause was the primary key for our custom doc type not matching the foreign key in the cms_document table.
Hope this helps someone!