Odd Error Message Insisting a Bug Report

I got this error immediately when performing a run test. "Could not find an instance by ID (set selection). I don’t notice anything that has changed, only that the error insisted on posting a bug report. At the time of the error, (4/8/2025) 10:00 PM MST, I have all beta features enabled. I am unable to reproduce the bug.


Here is my system information:
Ryzen 5 3600
GTX 1070 FTW
48 GB DDR4 Memory
Asus B4500-F Motherboard
Windows 10 Home Build 19045

1 Like

Just to follow up with another since the stack changed. For what it’s worth I only encounter this error after switching to server view while initially testing on the client.

I also encountered another strange bug, no errors were given. It was the same case where I went to server view from client. Not only were there duplicates of every service in the explorer, but everything was under incorrect parents. The best example from the linked video is the mob that apparently replaced the player StarterPack. This was not visible from the client’s explorer and had no impact on gameplay.

Adding to this bug report:

Reproduction Steps not known.

Steps leading to the error:

  • I opened my place (lets call it Place A)
  • I had copied a set of GUI Objects from other place (lets call this one Place B) to import
  • I tried clicking on StarterGui in Place A to insert into but the error was thrown.
  • Clicking on ANY explorer element leads to this error.

My thinking: Could be related to the recent explorer update but I figure you guys figured as much.

I can provide the place file upon request. I cannot DM it to @bug-files since its 48 MB, and I do not wish to upload proprietary code to a data hosting service.

1 Like

Replying here as it seems to be the first report of this error. I got this error by:

1: Joining a playtest with team create and the new explorer enabled
2: Debugging with breakpoints
3: Expanding any service in the explorer. I couldn’t see any other object.

Here’s a full video. I turned off any output my game makes. There are some bonus errors, too!

When the Double connection with PlayServer error doesn’t occur, the explorer works as intended. Turning team create off and on made the bug escape. I didn’t do anything special to trigger the bug, I think.