## TL;DR

Using async mode in the Wolfram Alpha API: only set async=true if your code follows up on the async flags, because flagged properties aren't in the first response. If you want everything in one shot, leave async off.

## Fix

1. Using async mode in the Wolfram Alpha API: only set async=true if your code follows up on the async flags, because flagged properties aren't in the first response.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are dealing with this situation.
- The symptom matches: Wolfram Alpha async=true means a second request, not faster results.

## When NOT to use

- Unrelated issues with a different cause.
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported per the linked source.

## Variant phrasings

### Wolfram Alpha async=true means a second request, not faster results

## Why it happens

Web (WolframAlpha .NET client README, danbopes/WolframAlpha): documents full support for async queries against the Wolfram Alpha Full Results API. With async mode, the response flags properties that require another request to fetch; if you want all results in a single response, do not use the async flag. Agents that enable async and then read the response as complete silently miss the flagged properties.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.