Azure / Azure/azure-powershell
Invoke-AzDataFactoryV2Pipeline return null and return httpclient timeout error 100
- Dominant language
- C#
- Stars
- 4.8k
- Forks
- 4.3k
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 54
Description
### Description
We have customer found try to get RunId from **Invoke-AzDataFactoryV2Pipeline** response. The RunId can be return intermediately. However, some time the RunId didn't return and response timeout.

However there isn't any way to set timeout time for **Invoke-AzDataFactoryV2Pipeline** https://learn.microsoft.com/en-us/powershell/module/az.datafactory/invoke-azdatafactoryv2pipeline?view=azps-10.0.0
Question:
Whether we can use this script Invoke-AzDataFactoryV2Pipeline to get Runid, other workarounds for it.
Whether we can extend the Http timeout? or Whether we can add a validate when run this script Invoke-AzDataFactoryV2Pipeline if RunId didn't return, extend the timeout time. Thanks in advanced.
### Issue script & Debug output
```PowerShell
RunId=Invoke-AzDataFactoryV2Pipeline -ResourceGroupName "xxx" -DataFactoryName "xxx" -PipelineName "xxxx"
```
### Environment data
```PowerShell
7.xx
```
### Module versions
```PowerShell
9.6.0 AZ
1.16.13 AZ.DataFactory
```
### Error output
_No response_
Contributor guide
Research direction
Start with Invoke-AzDataFactoryV2Pipeline in the Az.DataFactory 1.16.13 module and compare the documented behavior with the supplied PowerShell reproduction and timeout output. Determine whether RunId retrieval and HTTP timeout handling are defined or configurable; done means documenting a supported workaround or identifying a reproducible change with appropriate coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, powershell
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100