I have ran into this problem before and this seemed to work for me. Hope this helps.
https://geonet.esri.com/thread/52888
The SQL Query is exactly what's stopping the annotation from getting created.
The composite relationship class allows for new annotation to get created as soon as a new feature in the related feature class is created. This process only happens at the exact moment that the new feature is committed to the database (before you ever modify attribute information). When a SQL Query is being used to limit the annotation that is seen in a particular anno class, the value(s) which match the SQL query must be present at the time the feature is created for the related anno to get created as well. In your case, they're not.
