How to fix a notification error

[mkakh]

I had used an app called misskey.tools on my server.
And, after deleting the linking of the tool and my account from the website, the error starts appearing.

When I see "Notifications from linked apps" from misskey, it says error.
To determine the cause of the error, I tried to issue i/notifications from the API console with the following params:

{
  limit: 10,
  sinceId: '0',
}

Then, this error are returned:

{
  message: 'Internal error occurred. Please contact us if the error persists.',
  code: 'INTERNAL_ERROR',
  id: '5d37dbcb-891e-41ca-a3d6-e690c97775ac',
  kind: 'server',
  info: {
    e: {
      message: 'Could not find any entity of type "AccessToken" matching: {\n    "id": "9gwh4l6b4j"\n}',
      code: 'EntityNotFoundError',
      id: '4f641f49-0fbf-4d2a-863e-f70a2bdcfaae',
    },
  },
}

If there is a good solution, I would like to know it. Thank you.

---

日本語での要約
misskey.toolsを自分のサーバーで使用した後，サイトから連携解除をしたところ，通知でエラーが表示されるようになりました．
「連携アプリからの通知」を切ればエラーが起きないことは確認しています．
上述のパラメータを使ってAPIコンソールからi/notificationsを実行すると上のエラーが表示されました．
もし解決方法をご存知でしたらご教示ください．よろしくお願いいたします．

[mkakh]

I have no idea about the reason but the problem resolved itself.
What I did is just to use my Misskey server/instance for 1 day.

I could not find the causes but since the problem is successfully resolved, I would like to close this question.
I hope the causes will be identified and resolved in the future.
Thank you.

[mkakh]

FYI:
I have confirmed that even though the notification field are correctly displayed without errors, the API console returns same error.
The followings are the params and response.

Params

{
  limit: 100,
  sinceId: '0',
}

Responce

{
  message: 'Internal error occurred. Please contact us if the error persists.',
  code: 'INTERNAL_ERROR',
  id: '5d37dbcb-891e-41ca-a3d6-e690c97775ac',
  kind: 'server',
  info: {
    e: {
      message: 'Could not find any entity of type "AccessToken" matching: {\n    "id": "9gwaw2mxb6"\n}',
      code: 'EntityNotFoundError',
      id: '44fdeed1-7662-41dd-a5a6-2dca26541678',
    },
  },
}

Even though I am curious the reason, but since my server/instance is for personal use and this error itself could not be a big problem.
So, I will leave this question closed.
Thank you.