Hi ​@fabricio.gaeta,

You’re correct that the Hide bot run window option becomes locked when the bot is associated with a queue that is currently In Use. This happens because the queue is actively linked to the automation deployment configuration, and AA prevents changes to certain settings while the queue is engaged.
Here’s how you can resolve this:

A queue status of In Use means it is tied to at least one automation (bot) or deployment configuration.
As long as the queue is linked, you cannot modify settings like Hide bot run window.

1. Check which automations use the queue

• Go to Queues in the Control Room.
• Click on the queue name → Associated Automations tab.
• Identify the bot(s) linked to this queue.

2. Unlink the queue from the automation

• Open the automation configuration (where you see the General Settings screen).
• Navigate to the Queue section.
• Remove the queue association (uncheck or delete the queue reference).
• Save the changes.

3. Verify queue status

• After unlinking, go back to Queues.
• The status should change from In Use to Available.

4. Edit General Settings

• Now you can unselect Hide bot run window.
• Save the automation again.

5. Re-link the queue (if needed)

• If the queue is required for your bot, you can re-add it after making the change.

Keep in mind that you need edit permissions on both the automation and the queue.

• If the automation is part of a deployment schedule, you may need to pause or delete the schedule before unlinking the queue.
• If multiple bots share the same queue, unlinking will affect all of them.