Thank you for the answer.
Typically what you say is correct.
Actually it is not using unique numbering all the way to the end of the same provisioning:
For example (log extract of a single provisioning):
[----] I, [2019-01-14T17:16:51.364265 #982:641108] INFO – : Q-task_id([miq_provision_24000000000830]) <AEMethod [/Ext_API/Integration/ServiceNow/CMDB/get_hostname]> Starting
[----] I, [2019-01-14T17:16:52.270343 #982:6d79848] INFO – : ----- Get ServiceNow Hostname Record ----- - uri => https://se-qa-api…net/servicenow/rest/api/vocr/serverhost
And it goes like that (number changes) every time a new state is reached during the provisioning workflow.
So multiply that by 3 or 4 concurrent provisioning requests, one can not follow the stream of a specific request as the numbering changes.