I would guess it's the time that is the problem - whatever service would produce an inline answer is presumably falling over, and the subsequent timeout is repo

I would guess it's the time that is the problem - whatever service would produce an inline answer is presumably falling over, and the subsequent timeout is reported as an error.