Roman Smirnov

@Young200808, Thanks for bringing up this issue! To ensure that we have the same understanding, as a first step, let me explain which situations are covered with the implementation of...

In addition, can you please share the log files from the Zeebe Client, Gateway, and Zeebe Broker?

@Young200808, Thanks for your reply; it is very helpful. > But... as you said, the 1.3.7 cannot solve this scenario ——“The Gateway request y times out before the Zeebe Broker...

@Young200808 and @jerry123888, just wanted to reach out to see if you have any questions regarding my last https://github.com/camunda/zeebe/issues/9221#issuecomment-1111983424?

@jerry123888, Sorry for not being responsive this week; it's a busy one. > ... and could you reproduce this issue? So far, I am not able to reproduce the issue....

Comment on this: > But, I would even go further and say that the issue you are observing is not related to the usage of the `LongPolling` feature. Just for...

@jerry123888, > i guess there is a misunderstanding about [...] from the above image, you can see there are 23 missing jobs,the 23 is equal to the gap between job7...

@jerry123888, no, I am still not able to reproduce the issue.

@jerry123888, can you please share the logs, therefore?

@jerry123888, The log statement `Failed to activate jobs for type...` is caused by a connection failure (which gets resolved after a while): ``` 2022-05-11 02:35:06.521 [ActivateJobsHandler] [gateway-scheduler-zb-actors-0] WARN io.camunda.zeebe.gateway -...