Closed SimonTod closed 2 years ago
One suggestion I could give, which I really like to see in the future :
This kind of error could be catched, and sent to whatever notifiers is configured. This way, I could have been warned earlier that there was a problem.
I imagine that in some cases (unfortunately not this one), a simple code update could solve the issue.
You're still running the old built .js
files. You'll either need to run npm build
after updating, or use npm run start:ts
rather than npm start
.
This kind of error could be catched, and sent to whatever notifiers is configured. This way, I could have been warned earlier that there was a problem.
npm run build
was the right solution. Thanks :+1:
Describe the bug
Application cannot login anymore. I get the next warning : "Failed to authenticate with GraphQL API, trying again" Then I get the next error : "Sid returned null"
Screenshots or Logs
Additional context
I am running the application without docker. It is configured with a custom cron and launches itself once every day and logs the output in a dated file.
It has been working until January 26.
Today I updated the code with
git pull origin master
andnpm install
commands.