--session-id now works with --continue or --resume when an SDK URL is supplied.
What's wrong with this entry?
Starting with --session-id alongside --continue or --resume used to require --fork-session. That combination is now also accepted when an SDK URL is supplied. The error text is otherwise unchanged.
Error: --session-id can only be used with --continue or --resume if --fork-session is also specified.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
--continueand--resumefailures now say what went wrongBoth mention continue resume
-
v2.1.221
Memory recall index is prewarmed at startup
Both mention continue resume
-
v2.1.229
remote-control --continue is documented as reattaching, not resuming
Both mention continue