Re-index API logs are not correlated

Indexer service's re-index API's all related logs are not correlated or incorrect when searched by correlation-id . We can find log entries by crawling over kind and related requests to publish message on service bus along with several unrelated log but none of the index-worker endpoints & storage calls can be fetched with correlation-id. Upon debugging, we found that indexer-queue service would replace the correlation-id by the message-id for the remaining workflow.