Similar to the task creation logic on Turing, that we retrieve a taskId at the end of a sendExtrinsic call, Xcm tasks should also return an Id, which is the message hash, for developers to be able to know what task is scheduled. Then, we use the message hash to find the taskId on Turing chain.
Similar to the task creation logic on Turing, that we retrieve a taskId at the end of a sendExtrinsic call, Xcm tasks should also return an Id, which is the message hash, for developers to be able to know what task is scheduled. Then, we use the message hash to find the taskId on Turing chain.