VLClean Plain comparisons of self-hosted media tools

How to keep request queues in sync across platforms for bot runners

Keep request queues in sync across platforms with a shared list, clear approval rules, and duplicate checks for bots running on several platforms.

By VLClean ยท

VLClean is published by the makers of Askarr and Watcharr, which are compared here alongside other tools.

Keep one shared list as the source for every request, agree on how each request is named, and check every queue against that list on a fixed day each week.

OptionRequest methodCost details
AskarrYou request a movie or show on Askarr, and your own Radarr and Sonarr add it. [1]The Free plan costs $0 and allows 10 requests a month. [1]
Request formPeople submit titles through a form, which sends each title to the shared list the owner reads. Check which platforms the form can reach before you rely on it.not published
Shared request listRunners add each title to one shared list, so every platform reads the same requests. Check which queues the list can reach, and whether each platform supports reading it, before you rely on it.not published

What you need before you start

Start by listing every platform your bots take requests from, and every place a request can be approved. Multiple platform bot runners need one agreed list that everyone reads from, so a title asked for on one platform does not sit unseen on another. Every platform must be able to read the shared list before it can receive the same requests. Write down who owns that list and who may approve, change, or remove a request.

Decide what counts as the same request on each platform. A movie title, a show name, and a link to the title may all point at one item, so agree on one way to name each request before any syncing starts. A title and a database link can identify the same movie or show. Keep a short note of the rules, such as whether duplicates are merged or kept as separate entries.

Choose where the shared list will live, and make sure every runner can reach it. Set a regular day for comparing the queues against that list.

Step by step

  1. Pick one shared list as the main list, and tell every bot runner to add requests only there.
  2. Agree on how a request is named and what identifies it, such as a title ID or a link to the title, so the same item matches on every platform.
  3. Write down who approves a request and whether it must be approved before it reaches a queue.
  4. Connect the shared list to each platform's queue using the method that platform supports, then try one request end to end before relying on the setup.
  5. Check the queues on a fixed day each week and compare them with the shared list, removing duplicates and stale requests.
  6. After the first week, ask the runners which requests went missing or appeared twice, and adjust the rules to fix those points.

Tools that can do it

Askarr is made by the team that publishes this site, VLClean. Askarr is a hosted website that works with existing Radarr and Sonarr. [1] You request a movie or show on Askarr, and your own Radarr and Sonarr add it. [1] You add Askarr to Radarr and Sonarr one time as an import list, and they read your requests from it. [1] Askarr never connects to your Radarr or Sonarr and never receives their API keys. [1]

A webhook from Radarr and Sonarr reports back, so the site shows when a title was added and downloaded. [1] You can try the dashboard with a throwaway demo account and sample data without signing in. [1] The Free plan costs $0 and allows 10 requests a month. [1]

Other tools are not described here. Before you pick one, check how it handles a request that is changed on one platform, how duplicates are merged, and whether it can reach each platform's queue.

Common mistakes to avoid

Avoid letting the same request live in two lists. When runners add titles in several places, separate lists can cause queues to differ and requests to be handled twice. Name one place for requests and say so to everyone.

Avoid setting up a sync without agreeing on approval. If no one knows who decides, requests can pile up or be added without review. Write the approval rule down before the first request arrives.

Avoid skipping the regular check. Queues change over time, and unwanted requests can remain without review.

Avoid giving access to accounts and keys without checking what they are used for. Keys are codes that let tools access accounts, so check the permissions before sharing them. Review what each tool asks for before you connect it to the shared list.

Frequently asked questions

How do multiple platform bot runners keep request queues in sync?

Keep one shared list as the single place requests are added, agree on how each request is named, and decide who approves a request before it reaches any queue. Check every queue against that list on a fixed day each week. Remove duplicates and stale requests, and ask the runners what went missing after the first week so you can adjust the rules.

Can Askarr keep request queues in sync with Radarr and Sonarr?

Askarr is a hosted website that works with existing Radarr and Sonarr. [1] You add Askarr to Radarr and Sonarr one time as an import list, and they read your requests from it. [1] Askarr never connects to your Radarr or Sonarr and never receives their API keys. [1] Check that this setup fits every platform your runners use before you rely on it.

Does Askarr need anything installed to sync requests?

Nothing is installed; you add Askarr as an import list in Radarr and Sonarr. [1] A webhook from Radarr and Sonarr reports back, so the site shows when a title was added and downloaded. [1] You can also try the dashboard with a throwaway demo account and sample data without signing in. [1]

How much does Askarr cost for sending requests?

The Free plan costs $0 and allows 10 requests a month. [1] Plus costs $3.99 a month for 50 requests a month. [1] Pro costs $6.99 a month for unlimited requests. [1] Compare these limits with how many requests your runners are likely to send each month before you choose a plan.

Does Askarr show a request history with live status?

Askarr's plans include a request history with live status. [1] Check whether the history covers requests from every platform your runners use.

The Free plan costs $0 and allows 10 requests a month. [1]

Try Askarr

Sources

  1. Askarr's own description of itself (the product of this site's publisher)

Related comparisons