Dynamic pipelines started failing on PR builds

[François Collins]

Since last week, we started getting random pipeline failures, only on PR builds. Branch commit builds are still working correctly.

The Forge Dynamic pipeline provider has not changed in months, then we started getting this error:

Configuration error

Selected Dynamic Pipelines provider Forge app is malformed and can't be invoked: There was an error invoking the function - request to https://bitbucket/2.0/repositories/%7Bd25a0246-3335-409c-bdcf-ac32826aa4c2%7D/%7Bc2f18ae2-b13b-48a9-97d6-9c6ea2ba7b47%7D/pip... (truncated)

Anybody have any idea why?

[François Collins]

And why only on PRs?

[François Collins]

I went back to the project, ran npm I and redeployed, keeping my fingers crossed it might help. But since the failures are random, it's hard to tell if it makes any difference.

[François Collins]

The developer console logs only show this:

FetchError: request to https://bitbucket/2.0/repositories/%7Bd25a0246-3335-409c-bdcf-ac32826aa4c2%7D/%7Bc2f18ae2-b13b-48a9-97d6-9c6ea2ba7b47%7D/pipelines_config/variables failed, reason:
at ClientRequest.<anonymous> (webpack://bitbucket-dynamic-pipelines-provider/node_modules/node-fetch/lib/index.mjs:1495:1)
at ClientRequest.emit (node:events:536:35)
at emitErrorEvent (node:_http_client:101:11)
at TLSSocket.socketErrorListener (node:_http_client:504:5)
at TLSSocket.emit (node:events:536:35)
at emitErrorNT (node:internal/streams/destroy:169:8)
at emitErrorCloseNT (node:internal/streams/destroy:128:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
type: 'system',
errno: 'ETIMEDOUT',
code: 'ETIMEDOUT'
}