Forum Discussion
Invoke Pipeline Failing With Error 2015 – “Value cannot be null. Parameter name: source”
- 9 months ago
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
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.