Error: The response (403) did not contain the expected <turbo-frame id="tf-main"> and will be ignored. To perform a full page visit instead, set turbo-visit-control to reload.
- Dominant language
- Ruby
- Stars
- 548
- Forks
- 168
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 28
Description
## Error
```
The response (403) did not contain the expected and will be ignored. To perform a full page visit instead, set turbo-visit-control to reload.
```
## Stack trace
```
../node_modules/@hotwired/turbo/dist/turbo.es2017-esm.js:3650 in FrameController.throwFrameMissingError
../node_modules/@hotwired/turbo/dist/turbo.es2017-esm.js:3646 in FrameController.handleFrameMissingFromResponse
../node_modules/@hotwired/turbo/dist/turbo.es2017-esm.js:3567 in FrameController.loadFrameResponse
```
## Tracking Details
- **Project**: exercism-js
- **Sentry**: [Error: The response (403) did not contain the expected and will be ignored. To perform a full page visit instead, set turbo-visit-control to reload.](https://thalamus-ai.sentry.io/issues/145220149/)
- **Culprit**: FrameController.throwFrameMissingError(@hotwired/turbo/dist/turbo.es2017-esm)
- **First seen:** Sep 6, 2026
Contributor guide
Research direction
Start with the Sentry report and the @hotwired/turbo stack trace, especially FrameController.loadFrameResponse and the request returning 403 for the tf-main frame. Reproduce the response in exercism-js and trace which request produces it. Done means the reported Turbo frame error is resolved or the intended full-page fallback is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100