# Request timeout encountered for request \[POST v1/exercise\] **URL:** \ **Category:** App Development\ **Tags:** daml, json-api, ledger-api\ **Created:** [October 26, 2023, 3:16pm UTC](https://forum.canton.network/t/request-timeout-encountered-for-request-post-v1-exercise/6903 "2023-10-26T15:16:52Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![bartcant](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/bartcant/32/823_2.png) [@bartcant](https://forum.canton.network/u/bartcant)\ **Post date:** [October 26, 2023, 3:16pm UTC](https://forum.canton.network/t/request-timeout-encountered-for-request-post-v1-exercise/6903/1 "2023-10-26T15:16:52Z")
HI Daml team We are encountering a strange issue in our enviroment where we received a timeout on our POST v1/exercise while we are not receiveing any timeouts on POST v1/query ANy insights on what could be the root cause ? ---
**Author:** ![cocreature](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/cocreature/32/36_2.png) [@cocreature](https://forum.canton.network/u/cocreature)\ **Post date:** [October 26, 2023, 3:18pm UTC](https://forum.canton.network/t/request-timeout-encountered-for-request-post-v1-exercise/6903/2 "2023-10-26T15:18:30Z")
I would take a look at the JSON API and probably more important the participant logs to see which parts takes long enough to produce a timeout. /v1/exercise actually commits a transaction while /v1/query doesn’t so it’s not surprising that they behave differently. ---
**Author:** ![bartcant](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/bartcant/32/823_2.png) [@bartcant](https://forum.canton.network/u/bartcant)\ **Post date:** [October 26, 2023, 4:53pm UTC](https://forum.canton.network/t/request-timeout-encountered-for-request-post-v1-exercise/6903/3 "2023-10-26T16:53:23Z")
Can you remand me on how we can access the participants logs ? I like to investigate this further. Our timeout is set to 30 seconds, so a simple “Archive” Exercise should not take the full 30 seconds We fixed the issue by re-starting our EKG pod for daml-json-api The strange thing is that this issue occurred in 2 different environments, but with fairly large (same size) databases, but we had not seen any performance degradation recently in either one recently. ---
**Author:** ![cocreature](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/cocreature/32/36_2.png) [@cocreature](https://forum.canton.network/u/cocreature)\ **Post date:** [October 26, 2023, 4:54pm UTC](https://forum.canton.network/t/request-timeout-encountered-for-request-post-v1-exercise/6903/4 "2023-10-26T16:54:14Z")
How did you configure your participant? By default it writes it to a log file. In a cluster deployment you usually configure it to write to stdout and rely on your cluster infrastructure to capture logs from all containers. ---
**Author:** ![bartcant](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/bartcant/32/823_2.png) [@bartcant](https://forum.canton.network/u/bartcant)\ **Post date:** [October 26, 2023, 4:56pm UTC](https://forum.canton.network/t/request-timeout-encountered-for-request-post-v1-exercise/6903/5 "2023-10-26T16:56:40Z")
We are still on 1.13 Daml SDK, so we have a farly simple EKG architecture. I just did a > kubectl logs on the pod to get the log information ---
**Author:** ![bartcant](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/bartcant/32/823_2.png) [@bartcant](https://forum.canton.network/u/bartcant)\ **Post date:** [October 26, 2023, 8:17pm UTC](https://forum.canton.network/t/request-timeout-encountered-for-request-post-v1-exercise/6903/6 "2023-10-26T20:17:53Z")
Hopefully soon we get to migrate our production servers to Canton 🙂