Malformed URL exception when making Soapcall reports the Item but not the activity ID

This is an example message that occurred when a bad URL was used to make a Soapcall:

000003A2 2021-01-27 14:13:19.835 16506 17070 "[10.194.174.29:9876

[caller:FjE7tx6EX3NQe3fF2GaMA6,local:FjE7tx6ys2nwX7MCC3FR9T]] ERROR: -1: Malformed URL (in item 11)"

This got me to the correct graph, but had there been multiple Soapcalls, the reference would not have been specific enough.

In an effort to make debugging this issue easier, it would be helpful if the activity ID of the Soapcall being made with a Malformed URL could be reported in the exception messaging that appears in the Roxie Log file (in a similar manner as activity IDs are reported in other exception contexts).

Something analogous to:

ERROR: 0: JOIN limit exceeded(10000) file '~thor::key::clueproperty::inqhist::inquiry::did_QA' [id=3696] (in item 17)"

afishbeck