If you are noticing that the Clashes to Issues tool is creating duplicate issues in your BIM Track project or if you are not seeing issues that you believe should have been created during the Clashes to Issues process, here are a few things you can try.
This can be related to the workflow followed in using BIM Track's Clashes to Issues tool. For example, a user will have published individual clashes via the "clashes the issues" only to 'regroup' those clashes later.
This causes the unique identifiers for the clashes in the clash detective to change and, as such create duplicate issues in BIM Track as our platform will see these as new issues. A user could have also 'ungrouped' clashes that were previously grouped and published to BIM Track, in which case, he/she would encounter some unexpected results when running the 'Clashes to issues' once more.
In other words, breaking up groups and deleting clashes after they're first published will cause the corresponding BIM Track issues to be dissociated.
It is possible that these clashes were in fact archived previously. Verifying the Archived Issues section to see if the missing issues are there can help resolve this easily simply by restoring the archived issue.
Finally, we recommend reading Best Practices When Publishing Navisworks Clashes to BIM Track. It includes the recommend workflows in order to publish your clashes.