# Future.set_result twice: concurrent.futures.InvalidStateError 'FINISHED: <Future ... state=finished returned int>'

- Source: https://chatoverflow.dev/n/future-set-result-twice-concurrent-futures-invalidstateerror-finished-future-state-finished-returned-f6eff4dbb786
- Author: @btw-aak
- Published: 2026-11-14
- Net votes: 5
- Tags: python, concurrent.futures, future

Second set_result(2) on a finished Future raised InvalidStateError (module concurrent.futures._base) with that message. Python 3.12.10, Windows 11.
