504 gateway timeout for long requests about mindaro HOT 7 OPEN

Thank you @simyco for reporting this issue, and sorry you encounter it.
Looking at the logs you provided, I can see that something went wrong but the error we get from .NET is very vague (System.IO.IOException: Unable to read data from the transport connection: Operation canceled). This would need more investigation on our side.

To help me understand the scenario better, could you please answer the below questions?

• Does Bridge work for shorter requests? Is this only reproducing for long requests?
• Is it expected from your side that these requests take that long? A 14400 seconds is quite long.
• Does this issue reproduce all the time, or is it only transient?

from mindaro.

Thank you @simyco for reporting this issue, and sorry you encounter it.
Looking at the logs you provided, I can see that something went wrong but the error we get from .NET is very vague (System.IO.IOException: Unable to read data from the transport connection: Operation canceled). This would need more investigation on our side.

To help me understand the scenario better, could you please answer the below questions?

• Does Bridge work for shorter requests? Is this only reproducing for long requests?
• Is it expected from your side that these requests take that long? A 14400 seconds is quite long.
• Does this issue reproduce all the time, or is it only transient?

Hello @daniv-msft thanks for your reply and your help :)
Here my answers:

• Yes, for short requests it works like a charm. It works also if i tune the request with this errorand i reduce the response
• no, the request that goes in error takes max 1 minute, online it works very good indeed(14400 seconds are just for test)
• Transient but it’s very rare that works good

If you need any other information, video or something i’m available to send you.

from mindaro.

@simyco Thank you for your reply and these clarifications!
This will need further investigation on our side, and I'm logging a bug so that we can track this.

Could you please let me know if the workaround you mention (tuning the request to reduce the response) is acceptable while we investigate this? Realistically, it will take a couple of days before we get to this one.

from mindaro.

Another parallel question @simyco: could you please let me know if your application relies on gRPC at some point? We received a similar report for a gRPC app, and I'm curious to know if these are related.

from mindaro.

I didn't intend to close: just clicked the wrong button. :)

from mindaro.

no

I didn't intend to close: just clicked the wrong button. :)

no worry :)

@simyco Thank you for your reply and these clarifications!
This will need further investigation on our side, and I'm logging a bug so that we can track this.

Could you please let me know if the workaround you mention (tuning the request to reduce the response) is acceptable while we investigate this? Realistically, it will take a couple of days before we get to this one.

with the workaround yes, sometimes from a pc it creates two jobs for the same subdomain (and so goes in conflict and block everything) but deleting both the jobs solves the issue (but this is another thing :) )

Another parallel question @simyco: could you please let me know if your application relies on gRPC at some point? We received a similar report for a gRPC app, and I'm curious to know if these are related.

we are not using grpc for now

from mindaro.

Thank you @simyco for the extra information! We're tracking this bug on our side, and we'll let you know when we have a fix for it.

from mindaro.