Resolution:
The main purpose of tracking is to track overall message flow from source to destination. When it involves a number of intermediate points, you can see that the tracking ID is getting longer. As the data is sent through the enterprise, each TIBCO application can add information about its operations to messages that pass through. Its length varies with each application.

Usually a unique Globally Unique ID (GUID) value is used as a tracking ID and the length of the GUID is 27 bytes.

If an incoming message does not have tracking information specified, TIBCO IntegrationManager (IM) uses a default format to create the GUID portion of the tracking information. However, if incoming messages have tracking information specified, then the Application-specific information is added to the message to trace the message back to its source using SDK addApplicationInfo() method.

**
tracking^={^id^="0TmHAV5fRJUBR-GrIN-vzyq-JZM" ^1^[1]="BW.ADBW_CRM_IRIS_PRV_01-ADBW_CRM_IRIS_PRV_01-02.CRM/System/IRIS/ActivacionPrepago/pd_ActivacionPrepago.process.Job-2458367"
^2^[2]= BW…..
***

The ID part of the tracking is the tracking id that would remain at 27 bytes. It gets generated at the first source of the data flow. ^1^[1], ^2^[2] and so on = Application-specific information added to the message to trace the message back to its source using SDK addApplicationInfo() method. For example, BW’s pd_ActivacionPrepago.process is adding that information after receiving the message from the source.
 
Tracking ID does not have a limit since a real production environment has many messages (in MBs) with a long tracking information list. Individual applications need to minimize the information being added to the tracking information. A, few applications can provide a way to reset the tracking id. For example, Job.resetTrackingId() can be used in IM to reset the tracking id.

What is the trackingID and what is the maximum size for the trackingID field in an RV message?