Browser Session Conflict

This guide explains the "Session Access Conflict" notification and how to resolve it.

What is a Browser Session Conflict?

Sable tries to associate sessions with a unique browser tab. When you see the notification:

Session Access Conflict Another browser tab may be controlling this session. Please use only one tab per session.

This means the system detected that a different browser tab is attempting to control the same session.

What Causes This Error?

This is a safety mechanism to prevent multiple event loops in the browser from controlling the same session. You will see the message if a browser tab detects another tab is trying to control a session.

There is one possible scenario where one tab could emit the warning message:

1. You are running a session in Tab A
2. You open the same session in Tab B
3. You close Tab A
4. Tab B is the only remaining tab but now shows the conflict notification because the session was originally controlled by Tab A

How to Fix It

If you have multiple tabs open. Close the tab showing the notification.

If you are down to one tab (described above) and you are still seeing the same error, you can re-associate an assessment with your single tab by doing the following:

1. Pause the running session - Click the pause button in the workspace to stop the current session activity
2. Reload the page - Refresh your browser tab (press F5 or Ctrl+R / Cmd+R)
3. Start the session again - Resume or restart the session from the refreshed tab

This re-establishes the browser tab fingerprint and allows you to continue working.

Best Practices

• Use only one browser tab per user.
• If you need to switch tabs, pause the session first
• If you accidentally open multiple tabs, close the extra tabs before starting a penetration test session