An absolute filepath causes the pipeline to skip the path generation
At the beginning of a transfer, the pipeline generates the file's local and distant paths, using all the elements of the transfer's context (like the rule's path, the server's path, etc...). However, in the case of a transfer resumption, in order to avoid re-generating a potentially erroneous path (and since it would be redundant anyway), the path generation step is skipped.
The problem is, to detect whether this is the transfer's first try or not, the pipeline checks if the file's local path is absolute or not (since the path generation always generates an absolute path). However, Waarp-Gateway DOES allow users to create transfers with an absolute path (in case they need to transfer a file which does not belong to the gateway's file structure). And thus, if the transfer is created with an absolute local path, this causes the remote filepath generation to be skipped as well.
To fix this, the pipeline should use a different mechanism to determine whether it should generate the paths or not.