Skip to content

Revert a change that causes long messageIds that can lead to failure in publishing

Sabarish K R E requested to merge sabz/revertTraceChanges into azure/m18-master

Reverts PR !751 (merged)

As part of the change being reverted, The UUID and the correlationID were being used as messaageID, to enable traceability. The change was causing failures when the input correlation ID was longer than 91 characters, as it was being appended with a random UUID that was 36 characters. Using string with > 128 characters as the messageId when publishing a message to ServiceBus leads to the publish operation failing.

We need to revert this change for now and tackle the traceability in a different way in future.

Edited by Sabarish K R E

Merge request reports