I’m struggling with an edge-case in my Queue-It implementation. The bot is written in Python and the queue navigation logic relies on Selenium with CDP hooks. Everything works until I try to reuse or transfer the queue token on a second device: the moment the new browser attempts to join, Queue-It rejects the request with a “token validation failed” response. I need someone who understands the Queue-It validation flow in depth and can pinpoint why the token becomes invalid when the device fingerprint changes. You’ll be free to probe the existing Python code, review the Selenium-driven navigation, and introduce whatever signing or header adjustments are required to keep the token accepted across devices. Deliverable: a patched, clearly commented Python script (or module) that lets me start a queue on one device and successfully continue it on another without triggering the validation error, along with a brief explanation of any new parameters or security considerations I should be aware of.