Anything I can do about frequent trigger-pipeline connection failures?
Asked by Jay Seletz:

I'm seeing frequent (nightly) failures of the trigger-pipeline pipe when it tries to trigger a pipeline:

```
Status: Downloaded newer image for bitbucketpipelines/trigger-pipeline:5.5.1
92
Traceback (most recent call last):
93
File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 537, in _make_request
94
response = conn.getresponse()
95
File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 466, in getresponse
96
httplib_response = super().getresponse()
97
File "/usr/local/lib/python3.10/http/client.py", line 1375, in getresponse
98
response.begin()
99
File "/usr/local/lib/python3.10/http/client.py", line 318, in begin
100
version, status, reason = self._read_status()
101
File "/usr/local/lib/python3.10/http/client.py", line 279, in _read_status
102
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
103
File "/usr/local/lib/python3.10/socket.py", line 705, in readinto
104
return self._sock.recv_into(b)
105
File "/usr/local/lib/python3.10/ssl.py", line 1307, in recv_into
106
return self.read(nbytes, buffer)
107
File "/usr/local/lib/python3.10/ssl.py", line 1163, in read
108
return self._sslobj.read(len, buffer)
109
TimeoutError: The read operation timed out
```

`This is happened quite often lately. I'm on the latest version of the pipe. This is forcing multiple manual reruns of scheduled pipelines across different Bitbucket repositories.`


Answers:
author: Igor Stoyanov
body: [@Jay Seletz](/t5/user/viewprofilepage/user-id/3570383) hi. We will consider to implement your feature request with retry functionality on trigger build.  
We will notify you when new pipe version will become available.  

Regards, Igor


author: Mark C
body: Hi [@Jay Seletz](/t5/user/viewprofilepage/user-id/3570383)  

<br />

Thank you for reaching out to the community.  
There seems to be a bug with the Pipes script, but it has been fixed since.

Would you be able to confirm if you're still experiencing the issue?  

Regards,  
Mark C

comments: author: Jay Seletz
body: Hi [@Mark C](/t5/user/viewprofilepage/user-id/1210823) -

I am on v5.5.1 of the pipe, I believe the latest. I still had several of these failures last night. The issue is intermittent but frequent enough to be a problem.

Thanks,

Jay


author: Mark C
body: Hi [@Jay Seletz](/t5/user/viewprofilepage/user-id/3570383)

We've had an incident last night that may have caused the problem. - <https://bitbucket.status.atlassian.com/incidents/g8dt567xgs49>

Could you check if the same problem is still happening?

Regards,

Mark C


author: Jay Seletz
body: It is still happening on occasion. Maybe add a retry if the first call to start the pipeline has a timeout error?


author: Mark C
body: Hi [@Jay Seletz](/t5/user/viewprofilepage/user-id/3570383)

Would you be able to try the latest version which is:

```
atlassian/trigger-pipeline:5.6.0
```

<br />

Let me know how it goes.  

Regards,  
Mark C


author: Igor Stoyanov
body: [@Mark C](/t5/user/viewprofilepage/user-id/1210823) - The feature [@Jay Seletz](/t5/user/viewprofilepage/user-id/3570383) asked is still in development.  

Regards, Igor


author: Igor Stoyanov
body: [@Jay Seletz](/t5/user/viewprofilepage/user-id/3570383) hi. We released [new version 5.7.0 of the pipe](https://bitbucket.org/atlassian/trigger-pipeline/src/5.7.0/), where retry feature was added.  

Please, provide feedback if that solved your issue.  

Regards, Igor


Tags: bitbucket-cloud

cloud

pipes