If after the creation of the asset, we shut down the pod with a breakpoint in this line:
The asset is never indexed (but it's presented on project explorer and also on git repo)
Basically, I classify this issue as an edge case and making business central identify that the index is corrupted is a costly resource operation (CPU/RAM).
Considering also that this issue has a workaround; open the asset on project explorer (user are able to visualize/modify it) and after a save operation the index for that asset is retriggered I propose:
- Create a new menu on settings like 'Maintance' visible for project owner/admin where the user will be able to retrigger the indexing for that specific project.