@JairoA27In order to actually test the robot activity, you need to run the robot from a stand-alone Runtime. I don't believe Studio actually registers properly with Robot Manager (although I am not positive about the technical explanation here). For your simple test, a message box doesn't make much sense, since that would simply block the robot from executing anything else as no one is there to respond to it. I would test using a simple automation that created a file or something that can happen without anyone present. You can even just write to the log and look for that message when your test is complete.

I first build my automation(s) and have them accept any parameters they need to complete the assigned task. This would not connect to the Robot Activity component at all. These would be extensively tested in Studio with varying inputs until I was satisfied with their performance. Once I was ready, I would create a new automation I refer to as an Activity Procedure. This has an entry point and a blank exit point (I usually omit this exit point in fact as it makes the next part easier). Inside of this automation, I pass whatever parameters come from my Robot Activity into this automation I just tested. After the automation, I then update the completion status of the Robot Activity and pass any output parameters. Lastly, I create another automation I call an Activity Event. This uses the ActivityStarted event from the Robot Activity to call the Activity Procedure. I wrap the Activity Procedure in a Try Catch and if an Exception occurs, I set the Completion status to DidNotComplete. This serves as a catch-all for any exception that gets missed elsewhere.