Skip to main content
Uzumaki
Navigator | Tier 3
May 6, 2025
Solved

"User is not a consumer of a pool" error when running bot with a queue

  • May 6, 2025
  • 3 replies
  • 166 views

Hello,

Has anyone seen this error before or have any idea what causes it?

My control room admin is trying to schedule a bot to run with queue and he is getting this error message. We have created a role for running bots with queue and assigned it to the user that is going to run the bot (in a device pool). 

Any other ideas on what throws this error are much appreciated thank you.

 

 

Best answer by Padmakumar

Hi ​@Uzumaki ,

 

As per the error, it is clear that your Runner is not a consumer of the Pool which you are trying to use for your automation. Please check again the Device pool and see if this User has been assigned with the Consumer access or not. 

 

Please refer below documentation in case of any clarification needed.

 

Create device pools

3 replies

Padmakumar
Premier Pathfinder | Tier 7
Premier Pathfinder | Tier 7
May 7, 2025

Hi ​@Uzumaki ,

 

As per the error, it is clear that your Runner is not a consumer of the Pool which you are trying to use for your automation. Please check again the Device pool and see if this User has been assigned with the Consumer access or not. 

 

Please refer below documentation in case of any clarification needed.

 

Create device pools

Padmakumar
CaptainPathfinder
Community AI Agent
May 7, 2025

That’s an interesting question, Uzumaki !

I think the following community members may be able to help 

@ChanduMohammad 

@Tamil Arasu10 

@Olatidoye 

@KhaledMostafaMe 

@Theertha K S 

@Marc Mueller 

@Vatsy 

@Zaid Chougle 

@madhu subbegowda 

@jackson 

@HARUN KUMAR 

@NewTushitha 

@Azhar Hossain 

@kdil 

I'm your friendly neighbourhood AI Agent! (it/they). I try my best to match you with the right questions - but in case I miss, please feel free to let me know!
Uzumaki
UzumakiAuthor
Navigator | Tier 3
May 7, 2025

Hi ​@Uzumaki ,

 

As per the error, it is clear that your Runner is not a consumer of the Pool which are trying to use for your automation. Please check again the Device pool and see if this User has been assigned with the Consumer access or not. 

 

Please refer below documentation in case of any clarification needed.

 

Create device pools

It looks like the user might not have had the correct queue role. So I guess this worked, thanks.