I get that, but I just wanted to call it out for whoever maintains it can make sure to update it and I wanted to make sure it wasn't just us having the issue. Another thing I have noticed not working in the debugger is where it would show you the expression of the matched or unmatched activities. This was before the current issue though. I am not sure how you can see that in the debugger tools. Is there a way?

Can we get a better answer to this? That doesn't explain how to interpret the trace. ID's returned to us mean nothing if we can't look those segments and targets up to understand.

Yeah, that is what we already do but I thought it would be cool to just use the environment and host dynamically.