@deepkaran.salooja, thanks for the reply.
I'm not talking about calling this command during an ongoing build. I'm taking about calling it when there is no build at that moment, but, it just so happens to be, that one of the indexes is already built, so we just need to built the other indexes that aren't.
In today's cloud environments, there is a minimal intervention from admin/system-eng. The build of the indexes and buckets are all created on an automatic deployment scripts. So it make sense to make this call for all needed indexes, assuming that if some of them are already there, they will just be skipped.