Aspera

 View Only
Expand all | Collapse all

Error code 417 when trying to stop transfer using the aspera-transfer sdk API

  • 1.  Error code 417 when trying to stop transfer using the aspera-transfer sdk API

    Posted Tue September 10, 2024 01:35 AM

    Hi, 

    Running into a unique problem where when I try to stop a running Aspera transfer using its transferID, I get an error code 417 with a description which says 'Transfer ID is not persistent transfer.' However, when I query the TransferInfo to get all current running transfers, I can pretty clearly see my transferID in RUNNING status. Does anyone know what I am doing wrong? 

    Attaching image: 



    ------------------------------
    Jerlyn Manohar
    ------------------------------


  • 2.  RE: Error code 417 when trying to stop transfer using the aspera-transfer sdk API

    Posted Wed September 11, 2024 01:02 AM

    Hi Jerlyn,

    A non-zero delay in the stop transfer call is only meant for transfers that are marked as persistent. In your case, since the transfer type is a regular file transfer, try specifying the delay as 0 and see if that fixes the issue.

    Hope that helps,

    David



    ------------------------------
    David Wosk
    ------------------------------

    Original Message