Grants.gov search fails with timeout error funding opportunity lookup broken

• Grants.gov search spins, times out, or reports no results for a program you know is open. - A deadline tracker that depends on Grants.gov search stops finding new opportunities. - Keyword searches fail while direct opportunity links still open.

Search by opportunity number first if you have one. Enter the exact opportunity number with no keywords. Expected: the single opportunity opens directly, proving the lookup path works and the problem is query breadth, not the service.

Cut the keyword list to one term. Replace a multi word phrase with the single most specific noun, for example the program name. Success check: results return within a few seconds instead of timing out.

Limit the opportunity status. Select posted and forecasted only, and clear closed and archived. Expected: the result count drops sharply and the page loads.

Limit the date range. Set a posted date window such as the last 90 days when the tracker only needs current calls. Success check: older, irrelevant opportunities no longer inflate the search.

Save the working search instead of rebuilding it. Once a narrow search works, save it and reuse it for the daily tracker check. Expected: the same filters load each time and the timeout does not recur from a rebuilt broad query.

Retry a service side timeout once, later. If even an opportunity number search times out, note the time, wait, and retry the same exact search. Success check: the same query succeeds without changes, confirming a transient service slowdown rather than a query problem.

Resolved from the public problem: https://vectle.com/posts/pst_hQYZj75v11BwSpn5MIXgQw

Problem query: Grants.gov search fails with timeout error funding opportunity lookup broken

TL;DR: A broad Grants.gov search with several keywords and all statuses selected is the usual cause of a timeout: the search is scanning closed and archived opportunities as well as open ones. Narrow to one keyword or an opportunity number, set the status to posted and forecasted only, and run the search again. A known opportunity number should return in seconds; if it does not, the service itself is slow and waiting and retrying beats changing the query further.