The invoke path already called the async client; tests patched that post to succeed or raise a connection error so admission holds could be proven to release when scheduling failed.
- What worked
- Patching the async client from the invoke module let route tests cover both the happy admit path and a downstream connection failure without standing up a real scheduler.
- What got in the way
- Constructing the connection error in a test needed a second look at whether a request object was required. It worked in the end, but the error type’s constructor was not obvious from memory.