# Error log about boundary

**URL:** <https://discuss.hashicorp.com/t/error-log-about-boundary/32765>\
**Category:** Boundary\
**Created:** [December 6, 2021, 7:34am UTC](https://discuss.hashicorp.com/t/error-log-about-boundary/32765 "2021-12-06T07:34:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![liu](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/liu/32/22881_2.png) [@liu](https://discuss.hashicorp.com/u/liu)\
**Post date:** [December 6, 2021, 7:34am UTC](https://discuss.hashicorp.com/t/error-log-about-boundary/32765/1 "2021-12-06T07:34:41Z")

</div>

hi，  
A little problem  
Boundary is now running perfectly, but when I search the log about ‘error’, the following message will appear

```json
{
    "id": "gxrh6epgeP",
    "source": "***",
    "specversion": "1.0",
    "type": "error",
    "data": {
        "error": "nil result from looking up auth token by public ID",
        "error_fields": {},
        "id": "e_TPfFrUqDpw",
        "version": "v0.1",
        "op": "auth.(verifier).decryptToken",
        "request_info": {
            "id": "gtraceid_As4pRwXAvxut3gwDuHbV",
            "method": "GET",
            "path": "/v1/scopes",
            "public_id": "at_NoulkkfiuQ"
        }
    },
    "datacontentype": "application/cloudevents",
    "time": "2021-12-06T02:07:46.605214343Z"
}

```

It didn’t seem to affect anything, and it only lasted for a short time,Can anyone explain it? I’d appreciate it

---

<div class="post-metadata">

**Author:** ![jimlambrt](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/jimlambrt/32/12946_2.png) [@jimlambrt](https://discuss.hashicorp.com/u/jimlambrt)\
**Post date:** [December 6, 2021, 6:34pm UTC](https://discuss.hashicorp.com/t/error-log-about-boundary/32765/2 "2021-12-06T18:34:31Z")

</div>

I believe this happens when a user initiates an OIDC auth-flow. The CLI or desktop is polling to see if the user has completed the flow and if there’s a token as a result. I believe there’s been a recent PR that stops this “false positive” error event from being emitted.