You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of getting a 404 error/page when an opportunity is accessed that no longer exists we're instead throwing 500 errors. This problem seems to have been introduced with Release 2025.02.19-1. This is a front end issue, the API is correctly responding with a 404. This caused the Cloudwatch Alert for FE 500 errors to fire off this morning, likely due to Google or other crawling based on the errors/minute counts. Likely will need to re-crawl affected pages via Google console once the issue has been resolved.
API request error at http://localhost:8080/v1/opportunities/10000000 (404): Could not find Opportunity with ID 10000000
Failed to render page title due to API error Error: Could not find Opportunity with ID 10000000
at throwError (src/services/fetch/fetcherHelpers.ts:117:12)
at jsonBody (src/services/fetch/fetchers/fetchers.ts:80:24)
at async getOpportunityDetails (src/services/fetch/fetchers/opportunityFetcher.ts:8:19)
at async Module.generateMetadata (src/app/[locale]/opportunity/[id]/page.tsx:42:38)
115 | throw new ForbiddenError(message, details);
116 | case 404:
> 117 | throw new NotFoundError(message, details);
| ^
118 | case 422:
119 | throw new ValidationError(message, details);
120 | case 408: {
[cause]: [Object]
}
Malformed error object
GET /opportunity/10000000 500 in 193ms
API request error at http://localhost:8080/v1/opportunities/installHook.js.map (404): Not Found
Failed to render page title due to API error Error: Not Found
at throwError (src/services/fetch/fetcherHelpers.ts:117:12)
at jsonBody (src/services/fetch/fetchers/fetchers.ts:80:24)
at async getOpportunityDetails (src/services/fetch/fetchers/opportunityFetcher.ts:8:19)
at async Module.generateMetadata (src/app/[locale]/opportunity/[id]/page.tsx:42:38)
115 | throw new ForbiddenError(message, details);
116 | case 404:
> 117 | throw new NotFoundError(message, details);
| ^
118 | case 422:
119 | throw new ValidationError(message, details);
120 | case 408: {
[cause]: [Object]
}
Malformed error object
Summary
Instead of getting a 404 error/page when an opportunity is accessed that no longer exists we're instead throwing 500 errors. This problem seems to have been introduced with Release 2025.02.19-1. This is a front end issue, the API is correctly responding with a 404. This caused the Cloudwatch Alert for FE 500 errors to fire off this morning, likely due to Google or other crawling based on the errors/minute counts. Likely will need to re-crawl affected pages via Google console once the issue has been resolved.
Reproducibility
I tried multiple times and saw the bug every time
How to reproduce the bug
Access an Opportunity ID that doesn't exist:
https://simpler.grants.gov/opportunity/358329
https://simpler.grants.gov/opportunity/1000000
Browser
Not applicable
Code of Conduct
The text was updated successfully, but these errors were encountered: