RuntimeWarning: coroutine 'fetch' was never awaited
An async function was called without await, so it never ran.
Exact message you may see
was never awaitedcoroutine was never awaited
Seen on:
Python
Meaning
Calling an async def function returns a coroutine object; nothing happens until it’s awaited or scheduled. The value you used is the coroutine, not the result.
Common causes
- Missing await
- Calling async functions from sync code
- Passing an async function as a sync callback
⚡ Quick fix
- Add await
- Use asyncio.run(main()) from sync entry points
- Schedule with asyncio.create_task(...)
Detailed fix by platform
Python
result = await fetch(url)
How to diagnose
- Call — Which call is missing await?
- Context — Sync or async caller?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- AbortError AbortError: The user aborted a request. / signal is aborted without reason
- async useEffect Warning: useEffect must not return anything besides a function, which is used for clean-up. It looks like you wrote useEffect(async () => ...)
- await outside async SyntaxError: await is only valid in async functions and the top level bodies of modules
Most viewed in Python
Other ways to find it
Where this error sits
Origin: Application & API. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026