set current threadId when theres no mechanism to rely on

[marandaneto]

📢 Type of change

• Bugfix
• New feature
• Enhancement
• Refactoring

📜 Description

set current threadId when theres no mechanism to rely on.

💡 Motivation and Context

exception had no threadId if it was not a exception mechanism and this makes the thread selector not happy on the dashboard.

💚 How did you test it?

unit test and debugging it.

📝 Checklist

• I reviewed submitted code
• I added tests to verify changes
• All tests passing

🔮 Next steps

[bruno-garcia]

makes sense to send it anyway but ideally the front end wouldn't rely on having thread id at all and just show the exception component.

[marandaneto]

makes sense to send it anyway but ideally the front end wouldn't rely on having thread id at all and just show the exception component.

yep I agree, but if you do send exception + threads, it should be like this so the current behavior would work without changes on the frontend.