Sometime WorkflowClient.start() is not registering the workflow for execution

Community Support
1

Hi,
Sometime WorkflowClient.start() is not registering the workflow for execution while checking more it seems we received 500 INTERNAL_SERVER_ERROR.

Does it mean temporal service is down? Our other Workflows are working fine. We suspect some issue at our end only as One of the Workflow is causing this.

Which in result givig Async Timeout Exception as well.

Log:

{
    "exceptionDescription": "org.springframework.web.context.request.async.AsyncRequestTimeoutException",
    "lines": [
        "org.springframework.web.context.request.async.TimeoutDeferredResultProcessingInterceptor.handleTimeout(TimeoutDeferredResultProcessingInterceptor.java:42)",
        "org.springframework.web.context.request.async.DeferredResultInterceptorChain.triggerAfterTimeout(DeferredResultInterceptorChain.java:81)",
        "org.springframework.web.context.request.async.WebAsyncManager.lambda$startDeferredResultProcessing$5(WebAsyncManager.java:442)",
        "java.base/java.util.ArrayList.forEach(ArrayList.java:1511)",
        "org.springframework.web.context.request.async.StandardServletAsyncWebRequest.onTimeout(StandardServletAsyncWebRequest.java:154)",
        "org.apache.catalina.core.AsyncListenerWrapper.fireOnTimeout(AsyncListenerWrapper.java:44)",
        "org.apache.catalina.core.AsyncContextImpl.timeout(AsyncContextImpl.java:134)",
        "org.apache.catalina.connector.CoyoteAdapter.asyncDispatch(CoyoteAdapter.java:135)",
        "org.apache.coyote.AbstractProcessor.dispatch(AbstractProcessor.java:242)",
        "org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:57)",
        "org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:894)",
        "org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1741)",
        "org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)",
        "org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)",
        "org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)"
    ],
    "id": "b0c0adac-1ca0-422e-b7f2-7412cd37f65d"
}
2

I don’t think frontend service would give you back a http response, do your workers connect to a proxy/lb or directly to temporal frontend?

Can you catch StatusRuntimeException on your WorkflowClient.start call and share its info?