# Exceptions in Client Poller

**URL:** <https://community.temporal.io/t/exceptions-in-client-poller/1025>\
**Category:** Community Support\
**Tags:** java-sdk, exception\
**Created:** [November 17, 2020, 8:19pm UTC](https://community.temporal.io/t/exceptions-in-client-poller/1025 "2020-11-17T20:19:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\
**Post date:** [November 17, 2020, 8:23pm UTC](https://community.temporal.io/t/exceptions-in-client-poller/1025/2 "2020-11-17T20:23:55Z")

</div>

The first exception happens when an activity reports completion after it timed out or workflow already closed. If it happens frequently It usually indicates that activity timeout is too small.

The second exception is benign and should be changed to the DEBUG level. It means that a new event was received by the service while the workflow task tries to complete the workflow. To handle this race condition without data loss the workflow task completion fails and the task is retried. See [this discussion](https://community.temporal.io/t/continueasnew-signals/1008) that explains how this mechanism is used to ensure that signals are not lost in the presence of such race conditions.

---

_[View the full topic](https://community.temporal.io/t/exceptions-in-client-poller/1025)._