API token timeout causes app failure and requires complex workaround to reset
@naglepuff is already working on this.
Since Sep 11, 2025.
Assessment
This issue has not been assessed yet.
Description
Description:
Users experience API token timeout after spending time reviewing files in the app. The system shows a 60-second warning but the promised refresh option is not functional. When timeout occurs, users see error: "Failed fetch Spectrogram: Request failed with status code 500: Failed to verify access with NABat API."
Current Workaround Required:
Navigate away from surveys tab in Partner Portal
Return to surveys tab
Re-find survey of interest
Re-locate file within survey
Expected Behavior:
Functional refresh option should be available when timeout warning appears
Users should be able to continue working without complex navigation workaround
Impact:
Blocks manual vetting workflow
Creates poor user experience
Prevents real usage of the application
Links:
#159
- Dominant language
- Python
- Stars
- 11
- Forks
- 3
- Avg merge
- 7d 18h
- Merged PRs (30d)
- 3
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Kitware/batai
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Task
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
war-and-code/dircue#200 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day