search

Hankintailmoitukset / hilma-api

11 stars 0 forks source link

Stuck notice - what to do? #198

Closed eduardsmirnov closed 8 months ago

eduardsmirnov commented 12 months ago

Notice ETS is 63d4cd56-3ec6-469d-8ebf-c111af689b39-01 Current status you can see in an attached screenshot. image

What should we do? Is it really our problem that you were not able to authorize to TED?

eduardsmirnov commented 12 months ago

I re-submitted it but still not clear why internal HIlma issues should bring to a notice being stuck

Havunen commented 12 months ago

We are looking into it

Havunen commented 12 months ago

Is this the same ets identifier for which you got the error response 63d4cd56-3ec6-469d-8ebf-c111af689b39-01 ?

Havunen commented 12 months ago

The only TedError in our production DB are about TED maintenance break: 

<html>
<head><title>503 Service Temporarily Unavailable</title></head>
<body>
<center><h1>503 Service Temporarily Unavailable</h1></center>
</body>
</html>
eduardsmirnov commented 12 months ago

@Havunen I re-submitted 63d4cd56-3ec6-469d-8ebf-c111af689b39-01 and also a couple of other notices.

But the main question is why you move a notice into the status which requires us to re-submit a notice.

Havunen commented 12 months ago

But the main question is why you move a notice into the status which requires us to re-submit a notice.

Ah, yes. We have a technical improvement about it. That fix should be available in our next release.

exttuosa commented 12 months ago

The fix going live in next release will only fix known retriable errors, such as 503 and similar codes. The original problem in this ticket (which seems to have been misconfiguration in TED's end) will not be retried. There currently is no way of knowing if a TED error is transient or not. They did promise to clarify this in the future releases though.