Forum Discussion

Saraswathi_k's avatar
Saraswathi_k
Helper I
9 months ago
Solved

Invoke Pipeline Failing With Error 2015 – “Value cannot be null. Parameter name: source”

Hello Team,

I am working on a Microsoft Fabric pipeline where the parent pipeline invokes two child pipelines:

  1. Onprem2Raw_PL – Copy source data from MySQL (on-prem) → Fabric Lakehouse Raw

  2. RawFiles2Bronze_PL – Copy Raw → Bronze folder

    My issue is: The Invoke Pipeline activity fails, even though everything works individually

    What I Verified:

    •  The on-premises data gateway is online

    • MySQL connection Test Connection = Successful

    • Copy Data activity in Onprem2Raw_PL → Preview Data works

    • No parameters added (all hardcoded paths)

    •  Child pipeline runs successfully by itself

    • Only the parent pipeline fails when invoking the child pipeline

      Question:

      Why is Fabric reporting that the source = null during Invoke Pipeline execution, even though preview and test connection succeed?
      Is this a known metadata issue?
      How can I force Fabric to refresh/rebuild the Copy Data source metadata?

  • Saraswathi_k   no so long ago, someone raised this exact same thing, in that case, it was a DB2 connection, here's the discussion  Re: Invoke Pipeline fails with Error code 2015: 'V... - Microsoft Fabric Community, 

    but the error was EXACLTY THE SAME "The child pipeline fails consistently with this error:  Fabric activity failed. 'Value cannot be null.  Parameter name: source '.

     

    I would recommed two actions ... 

    #1. Report this to MSFT, I think there's a bug flying around on the new Invoke Pipeline task 

    #2. Use the legacy Invoke Pipeline and try, on that case, that was the workaround.... the legacy is working fine .

     

    Best of lucks! If you find this info. useful, I would appreciate a thumb-up, and if it fixes your issue, mark as solution for other people facing the same... all the best 

3 Replies

  • Saraswathi_k   no so long ago, someone raised this exact same thing, in that case, it was a DB2 connection, here's the discussion  Re: Invoke Pipeline fails with Error code 2015: 'V... - Microsoft Fabric Community, 

    but the error was EXACLTY THE SAME "The child pipeline fails consistently with this error:  Fabric activity failed. 'Value cannot be null.  Parameter name: source '.

     

    I would recommed two actions ... 

    #1. Report this to MSFT, I think there's a bug flying around on the new Invoke Pipeline task 

    #2. Use the legacy Invoke Pipeline and try, on that case, that was the workaround.... the legacy is working fine .

     

    Best of lucks! If you find this info. useful, I would appreciate a thumb-up, and if it fixes your issue, mark as solution for other people facing the same... all the best 

    • Saraswathi_k's avatar
      Saraswathi_k
      Helper I

      Thank you for sharing the link!

      I had the same error “Value cannot be null. Parameter name: source”.
      After trying your suggestion, I switched to the legacy Invoke Pipeline, and it worked for me as well.

      So yes — the new Invoke Pipeline activity definitely seems to have a bug.
      Thanks a lot for the guidance!

  • I had the same error “Value cannot be null. Parameter name: source”.
    After I switched to the legacy Invoke Pipeline, and it worked for me as well.

    So yes — the new Invoke Pipeline activity definitely seems to have a bug.