Overview Dictionary Bot policy Bot Approvals Group Guide Noticeboard Newsletter Bot Requests Requests for Approval Adminbots {{BAG Tools}} Creating a Bot List of bots Activity monitor Status report History Types

All editors are encouraged to participate in the requests below – your comments are appreciated more than you may think!

Shortcuts WP:BRFAWP:BRFA WP:RFBOTWP:RFBOT

To run a bot on the English Wikipedia, you must first get it approved. Follow the instructions below to add a request. If you are not familiar with programming, consider asking someone else to run a bot for you.

Operator: DreamRimmer (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 10:06, Tuesday, October 28, 2025 (UTC)

Automatic, Supervised, or Manual: automatic

Programming language(s): Python

Source code available: TBD

Function overview: Mark as reviewed all the redirects in the NPP queue that are bolded in the lead of the target article.

Links to relevant discussions (where appropriate): Wikipedia talk:New pages patrol/Reviewers#Redirect backlog

Edit period(s): Daily

Estimated number of pages affected: Process all redirects in the NPP redirect queue, which currently contains over 37,000 redirects, and mark those that meet the criteria. The first run will cover around 10% of the total redirects.

Exclusion compliant (Yes/No): No

Already has a bot flag (Yes/No): Yes

Function details: Mark as reviewed all the redirects in the NPP queue that are bolded in the lead of the target article.

• Support. Consensus at Wikipedia talk:New pages patrol/Reviewers#reviewing by bot all redirects that are bolded in the lead of the target article. –Novem Linguae (talk) 10:17, 28 October 2025 (UTC)[reply]
• {{BAG assistance needed}} Tenshi! (Talk page) 00:14, 5 November 2025 (UTC)[reply]

  I think J947 is raising an interesting objection in the discussion above. I'd like to see if we can talk through it a bit; it might be that consensus is still clearly in favor of this, but it hasn't been that long and no one has really engaged with it. — The Earwig (talk) 01:54, 5 November 2025 (UTC)[reply]

  Hello friends. It's been a couple weeks and it looks like the situation hasn't changed. Wikipedia talk:New pages patrol/Reviewers#reviewing by bot all redirects that are bolded in the lead of the target article has a pretty strong consensus for this bot task, with many participants and only one objection. Can this bot task proceed? Thanks. –Novem Linguae (talk) 06:53, 19 November 2025 (UTC)[reply]

  I've just seen that (not sure how I missed it before), and I agree with the objection (and have noted such on the linked page). Thryduulf (talk) 10:43, 19 November 2025 (UTC)[reply]

  Noting two new opposes in the last three days.

   On hold. For now. Primefac (talk) 12:45, 22 November 2025 (UTC)[reply]

Operator: Sisyph (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 22:00, Thursday, October 23, 2025 (UTC)

Function overview: Update tennis rankings and career prize money for women tennis players

Automatic, Supervised, or Manual: Automatic

Programming language(s): pywikibot

Source code available: fr:Utilisateur:DSisyphBot/Script/màj tennis.py

Links to relevant discussions (where appropriate):

Edit period(s): weekly (following WTA updated ranking)

Estimated number of pages affected: ~100 pages per week

Namespace(s): main

Exclusion compliant (Yes/No): Yes

Function details: 1/ Get WTA profile from wikidata page. 2/ Get data (best ranks + career prize money) from WTA profile. 3/ Update best ranks if needed + update prize money if > $US10000 to not spam edit for "small" earns.

The bot has already edits pages on one loop. For inactive players, it is a one shot. For active players, there will be a weekly check. Next step will be to do it for men tennis players with atptour.com site to get ranks data. --Sisyph (talk) 22:00, 23 October 2025 (UTC)[reply]

I've reviewed a lot of the edits and they seem fine to me. This saves hours of manual labour on updating rankings and prize money. Do you feel it would be within scope for a bot to be able to update the win and loss totals as well? The only downside is that we'll have to follow the bot and manually update the 'last updated' timestamp at the bottom of the infobox, unless the bot is smart enough to do that too. Spiderone^{(Talk to Spider)} 13:53, 26 October 2025 (UTC)[reply]

I note when something similar came up recently, a suggestion was that this sort of thing should be done in Wikidata, or failing that a centralized data page (i.e. a template, a module, or a .json page that's read by a module), instead of making repeated bot edits to individual articles. Anomie⚔ 14:10, 26 October 2025 (UTC)[reply]

 Note: This bot appears to have edited since this BRFA was filed. Bots may not edit outside their own or their operator's userspace unless approved or approved for trial. AnomieBOT⚡ 22:07, 26 October 2025 (UTC)[reply]

Hello, for win / loss total, it is posssible [1]. For the current rank, my issue is to get the date of this rank and mentionnent in the infobox, it must be : <!--ONLY UPDATE WITH LAST DATE THIS RANKING WAS HELD, NEVER UPDATE UNTIL THE WTA WEBSITE IS UPDATED (date should be a Monday), THE REFERENCE DOES NOT NEED TO BE UPDATED -->, so not possible so far, it doesn't seem to have sources to find it. For update field, it can be updated if already existing [2]. For wikidata centralization, for sure it will be the best option, like ELO rank for chess players. But I am not skilled to initiate it for tennis players. I will be able to update wikidata if one day it is implemented. Sorry to have edit 2 more pages it was for the 2 examples --Sisyph (talk) 22:25, 26 October 2025 (UTC)[reply]

@Sisyph: Do not allow the bot to edit the English Wikipedia again until it is approved for trial by a member of the Bot Approvals Group. This will include use of the {{Bot trial}} template. If the bot does edit again, the bot account may be blocked until a trial is approved. Anomie⚔ 23:17, 26 October 2025 (UTC)[reply]

Just to point out it is pointless this bot being used to update career prize money in tennis player infoboxes when the rest of the statistics remain unchanged. Either get this thing to update everything (win/loss records, rankings, prize money) or stop doing it. The current practice is misleading and inaccurate. I have posted this message on the bot's talk page too. Shrug02 (talk) 09:02, 29 October 2025 (UTC)[reply]

Hello Shrug02, I can understand your view. I don't agree with inaccurate, but I can confess that only update the prize money could be pointless for some players. My fear to not update this field in the infobox independently (because, yes the bot could be only update when the rankings or win/loss records change), is to be in front a never update (by bot), for players who reach their highest rank. Currently the bot update the prize money when it changes over $10,000, to not update for unsignificant earnings. But I can change to minimum $10,000 AND 5% of wikipedia data current prize money. It means for valuable player already reach $1 million, it represents $50,000 difference before edit. --Sisyph (talk) 23:35, 29 October 2025 (UTC)[reply]

I agree with Anomie, it would be better for the bot to edit one page, as is done with Module:ATP rankings. Can the bot be modified to do this? Primefac (talk) 12:50, 22 November 2025 (UTC)[reply]

Given the previous concerns about the bot making selective edits (I agree that statistics are likely viewed holistically, so only editing prize money could cause discrepancies), maybe it's worthwhile to consider the bot to update multiple statistics (beyond prize money) in one comprehensive template on Wikidata? asoundd 14:35, 1 December 2025 (UTC)[reply]

Operator: Aydoh8 (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 04:28, Sunday, October 19, 2025 (UTC)

Function overview: Replacing DMY formatted dates on articles with {{use MDY dates}} tags, and vice versa.

Automatic, Supervised, or Manual: Supervised

Programming language(s): Python

Source code available: [3]

Links to relevant discussions (where appropriate):

Edit period(s): Daily

Estimated number of pages affected: Will check one page approximately every 3-5 seconds. If that page does include dates needing to be changed, it will take approximately 7 seconds (in testing) to complete before checking the next page.

Namespace(s): Mainspace

Exclusion compliant (Yes/No): Yes

Function details: This bot will run through pages in mainspace. It will check the page for any {{use dmy dates}} or {{use mdy dates}} templates, and if exactly one of those is found, it will check for any dates (both in plaintext and in certain date templates) to ensure they are correctly formatted, otherwise it will correct them. I have conducted testing in the bot's userspace (see the bot's contribs) and have fixed any of the bugs discovered in testing. As a side note, I have added an exception for references to the January 6 United States Capitol attack by blocking the change of January 6 on any article to 6 January (may lead to false negatives but I would rather false negatives over false positives).

This seems very liable to run into WP:CONTEXTBOT issues. How will your bot avoid editing direct quotes, things besides "January 6", and so on? Glancing at your linked code, it looks like it would even break links and filenames if they happen to contain something that resembles a month and year. Anomie⚔ 00:57, 21 October 2025 (UTC)[reply]

Agreed. If I were this editor, I would plan to make at least 1,000 supervised edits at a reasonable pace using the intended script, checking each of the script's proposed changes before and after publishing. I think I would find that the script has some shortcomings. If you can address them, this bot process may be worth pursuing. Note that editing in this manner does not violate the bot policy, although you may find it tedious. – Jonesey95 (talk) 14:51, 21 October 2025 (UTC)[reply]

Note that editing in this manner does not violate the bot policy Agreed. It would fall under Wikipedia:Bot policy#Assisted editing guidelines, which has some useful information. Anomie⚔ 15:05, 21 October 2025 (UTC)[reply]

• Is there a specific reason you are using RandomPageGenerator? Using a generator that directly fetches pages transcluding these two templates would be more efficient, as the current method skips around 60 to 70 percent of pages without changes. Also, the nobots check in your code is unnecessary since Pywikibot by default already avoids editing pages with that template. – DreamRimmer ■ 03:49, 22 October 2025 (UTC)[reply]
• {{Operator assistance needed}} Please answer the above questions that have been raised. Tenshi! (Talk page) 01:32, 29 October 2025 (UTC)[reply]

  I'm going to completely redo the page generation part of this task, so I will put this task on hold for now. I have a few others that I am working on. Aydoh8^{[what have I done now?]} 04:36, 29 October 2025 (UTC)[reply]

   On hold. For AnomieBOT. Tenshi! (Talk page) 15:15, 5 November 2025 (UTC)[reply]

Operator: Phuzion (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 22:14, Tuesday, November 11, 2025 (UTC)

Automatic, Supervised, or Manual: automatic

Programming language(s): AWB

Source code available: AWB

Function overview: Will replace {{infobox mapframe}} instances in {{Infobox station}} using a substitution template

Links to relevant discussions (where appropriate): Bot request

Edit period(s): One time run

Estimated number of pages affected: ~3,900

Exclusion compliant (Yes/No): Yes

Already has a bot flag (Yes/No): Yes

Function details: This task will, in two cases, insert a substitution template into instances of {{Infobox station}}: The first case is when |mapframe= is equal to yes and when |mapframe-custom= includes the text {{Infobox mapframe. The second case is when |embedded= begins with {{Infobox mapframe.

This substitution template will replace the embedded mapframe template with native mapframe parameters of {{Infobox station}}, simplifying the layout of the infobox and taking advantage of the native parameters.

I have performed a couple of test edits on my main account to demonstrate what will be done: embedded, mapframe

From a technical perspective, this is a simple AWB find/replace with a fairly simple regex. The list of articles was pulled from Petscan.

Happy to answer any questions!

Just wanted to voice my support for this run! Happy to help check the diffs for any issues. -Zackmann (^{Talk to me}/_{What I been doing}) 22:18, 11 November 2025 (UTC)[reply]

@Phuzion: one issue to watch out for... Nested infoboxes also calling the mapframe. See Allenhurst station for example... These should probably be skipped by your bot and manually fixed... -Zackmann (^{Talk to me}/_{What I been doing}) 05:57, 15 November 2025 (UTC)[reply]

{{BAG assistance needed}} Tenshi! (Talk page) 16:11, 19 November 2025 (UTC)[reply]

• Approved for trial (50 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Please make sure to review Zackmann’s comment above about the nested infoboxes before you proceed with the trial edits. – DreamRimmer ■ 10:08, 20 November 2025 (UTC)[reply]

Operator: Scaledish (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 12:58, Tuesday, September 16, 2025 (UTC)

Automatic, Supervised, or Manual: automatic

Programming language(s): Python

Source code available: GitHub

Function overview: Update US settlement census data

Links to relevant discussions (where appropriate): Request 1 · Request 2

Edit period(s): Yearly; new estimates released yearly

Estimated number of pages affected: Unknown, likely low 10 thousands

Exclusion compliant (Yes/No): Yes

Already has a bot flag (Yes/No): No

Function details:

• Add the results of the latest U.S. Census to all instances of {{US Census population}} & {{{Infobox settlement}}, adding the appropriate ref
• Remove estimates from {{US Census population}} & {{{Infobox settlement}} in the case that the estimate was made before the latest census, per Category:Pages using US Census population needing update
• Add new estimates to both templates, if possible
• Does not change or add statements like "As of the 2010 census"
• Generally conservative.

• Doesn't add to a template if it sees there are multiple of it on the same page
• Doesn't overwrite info if it is same age or newer

Supervised Test 1 & Supervised Test 2 Scaledish! Talkish? Statish. 13:06, 16 September 2025 (UTC)[reply]

Approved for trial (50 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Since this is your first bot task, I am treating this as a one-off task. For future years, a new BRFA will be needed, and then we can see if it can be approved to run annually. – DreamRimmer ■ 13:58, 24 September 2025 (UTC)[reply]

{{Operator assistance needed}} Anything on the trial? Tenshi! (Talk page) 11:52, 7 October 2025 (UTC)[reply]

Hi, the trial is not yet concluded.

As part of the trial, the bot was ran twice, both times being stopped due to eventually forming a false association between the database and the article. This lead to the conclusion that the match script needs to be improved significantly, which I will do but haven't yet had the time. I still believe a reasonable fix is possible. Likely, as part of this, a semi-supervised confidence approach will be adopted where, if confidence isn't overwhelmingly high, the association is sent for manual review.

Also as part of the trial, an additional issue was identified. If the infobox population is from <2010, is cited using a named reference, and elsewhere in the body that reference is referenced, a cite error is caused because those references are now dangling. This may be a simple fix, but needs to be implemented.

When both of these fixes are implemented, I plan to resume the bot for the remaining ~25 trial edits. Afterwards, I will request an additional 50 trial edits. Scaledish! Talkish? Statish. 17:16, 7 October 2025 (UTC)[reply]

{{Operator assistance needed}} Any progress on the fixes? Tenshi! (Talk page) 12:32, 7 November 2025 (UTC)[reply]

I apologize for the delay, my real life workload is roughly cyclical—you can see that reflected in my xtools stats. I expect to be able to work on it again within a week or two. Scaledish! Talkish? Statish. 19:55, 7 November 2025 (UTC)[reply]

Operator: GalStar (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 21:00, Wednesday, July 2, 2025 (UTC)

Function overview:

Automatic, Supervised, or Manual: Automatic

Programming language(s): Rust/Python

Source code available: Uses mwbot

Links to relevant discussions (where appropriate): Wikipedia:Bot_requests#Redirects_related_to_those_nominated_at_RfD and Wikipedia talk:Redirects for discussion#Avoided double redirects of nominated redirects

Edit period(s): Continous

Page: Wikipedia:Redirects_for_discussion

Exclusion compliant (Yes/No): Yes (but N/A)

Adminbot (Yes/No): No

Function details:

• Look at each RFD on each RFD Page
• Determines whether there are any other redirects, in any namespace, that meet one or more of the following criteria:
  • Are marked as an avoided-double redirect of a nominated redirect
  • Are redirects to the nominated redirect
  • Redirect to the same target as the nominated redirect and differ only in the presence or absence of non-alphanumeric characters, and/or differ only in case
• If the bot finds any redirects that match and which are not currently nominated at RfD, then it should post a message in the discussion (final details about the message are TBD, but the bot request outline the general point). The bot limits the length of it's message, ensuring that the RfD is not over-cluttered.

Thanks for working on this GalStar, but it's not clear whether it is checking for redirects that differ only in the presence/absence of diacritics? Thryduulf (talk) 23:41, 2 July 2025 (UTC)[reply]

Diacritics fall under non-alphanumeric characters. GalStar (talk) (contribs) 16:48, 3 July 2025 (UTC)[reply]

Approved for trial (30 days). Please provide a link to the relevant contributions and/or diffs when the trial is complete. – DreamRimmer ■ 06:35, 8 July 2025 (UTC)[reply]

{{Operator assistance needed}} Anything on the trial? Tenshi! (Talk page) 18:54, 4 August 2025 (UTC)[reply]

Am on vacation, expect updates in a few days. GalStar (talk) (contribs) 15:48, 11 August 2025 (UTC)[reply]

 On hold until RfD accepts my proposal to use a new templating system, one that is more friendly to bots. — Preceding unsigned comment added by GalStar (talk • contribs) 05:57, 25 August 2025 (UTC)[reply]

 On hold. For AnomieBot. Tenshi! (Talk page) 15:12, 25 August 2025 (UTC)[reply]

@GalStar: Is there a reason why you can't just use regex to find each nomination and use the information from that? For example, TenshiBot's unlisted copyright problems report looks for copyright problems in the subpages which use substed {{article-cv}} (regex: [4], although the script knows the names of the pages already, I imagine it wouldn't be too hard to get that from RfD subpages). Tenshi! (Talk page) 20:57, 6 September 2025 (UTC)[reply]

Thanks for pointing this out. I was trying to do this the "right" way with wikicode parsing, but I'll take a look at regex. GalStar (talk) (contribs) 04:13, 8 September 2025 (UTC)[reply]

{{Operator assistance needed}} Any update? – DreamRimmer ■ 09:17, 29 September 2025 (UTC)[reply]

I'll take a look this week and see if I can finish implementation. GalStar (talk) (contribs) 05:20, 5 October 2025 (UTC)[reply]

A user has requested the attention of the operator. Once the operator has seen this message and replied, please deactivate this tag. (user notified) Anything on the proposal or implementation? Tenshi! (Talk page) 15:13, 5 November 2025 (UTC)[reply]

Operator: Trappist the monk (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 01:39, Monday, November 10, 2025 (UTC)

Function overview: replace wikitable-based ship infoboxen with Module:Infobox-based {{Infobox ship}}

Automatic, Supervised, or Manual: Automatic

Programming language(s): c#

Source code available: see User:Monkbot/task 22: Replace table-based ship infoboxen

Links to relevant discussions (where appropriate): Wikipedia:Templates for discussion/Log/2022 April 30 § Template:Infobox ship begin; subsequent sporadic discussions at:

• Wikipedia:Templates for discussion/Holding cell § Infoboxes
• Template talk:Infobox ship § Introduction
• Template talk:Infobox ship § Development and Improvement discussions
• Template talk:Infobox ship § Proposal for a new merged version
• Template talk:Infobox ship § Update
• Wikipedia talk:WikiProject Ships § ship infoboxen.

Edit period(s): one time

Estimated number of pages affected: ~41000

Namespace(s): mainspace

Exclusion compliant (Yes/No): yes

Function details: see User:Monkbot/task 22: Replace table-based ship infoboxen

• {{BAG assistance needed}} Tenshi! (Talk page) 13:59, 17 November 2025 (UTC)[reply]

  @Tenshi Hinanawi: Monkbot 22 is not your bot. Are you sure you added the above to the correct request?

  —Trappist the monk (talk) 14:11, 17 November 2025 (UTC)[reply]

  Yes, I'm sure that I added it to the correct request. Tenshi! (Talk page) 14:26, 17 November 2025 (UTC)[reply]

  The documentation for {{BAG assistance needed}} says:

  "This is intended for use if urgent attention is needed or if a request is being neglected (wait seven days first)." (quotes in original)

  What is it about this BRFA that requires 'urgent attention'? Surely it can't be because 7 days 12 hours 20 minutes had elapsed since the BRFA was posted... Can it?

  —Trappist the monk (talk) 14:55, 17 November 2025 (UTC)[reply]

  It doesn't inherently require urgent attention, and that was why I put the template here, yes. Tenshi! (Talk page) 15:48, 17 November 2025 (UTC)[reply]

  I must echo TTM here; the BAG folk are all volunteers, and for a non-urgent task such as this one (and I mean really non-urgent, given the merge has been listed since 2022!) you should not be banging on the doors of BAG members to get our attention. I'm not going to ask/tell you to stop pinging us ever but please do be considerate, especially since I have all but been ignoring your pings using the {{@BAG}} template recently. Primefac (talk) 12:41, 22 November 2025 (UTC)[reply]

  Okay, I'll keep that in mind from now on. Tenshi! (Talk page) 14:12, 22 November 2025 (UTC)[reply]

Approved for trial (100 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Big count I know, but this is a merge that has been in limbo for a long time because of the complexity and I want to make sure we hit as many possible outliers as possible in the trial. Primefac (talk) 12:41, 22 November 2025 (UTC)[reply]

Trial complete. diffs.

—Trappist the monk (talk) 20:24, 22 November 2025 (UTC)[reply]

Noting that I'm not seeing any issues here but will leave it for a week just to see if there is any feedback on the process. Primefac (talk) 22:15, 23 November 2025 (UTC)[reply]

Bots that have been approved for operations after a successful BRFA will be listed here for informational purposes. No other approval action is required for these bots. Recently approved requests can be found here (edit), while old requests can be found in the archives.

• CSD U6 Bot (BRFA · contribs · actions log · block log · flag log · user rights) Approved 10:05, 23 November 2025 (UTC) (bot has flag)
• BunnysBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 7) Approved 12:59, 22 November 2025 (UTC) (bot has flag)
• BunnysBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 8) Approved 12:38, 22 November 2025 (UTC) (bot has flag)
• GalliumBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 6) Approved 10:42, 17 November 2025 (UTC) (bot has flag)
• DreamRimmer bot II (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 6) Approved 10:05, 10 November 2025 (UTC) (bot has flag)
• Dušan Kreheľ (bot) (BRFA · contribs · actions log · block log · flag log · user rights) (Task: IX) Approved 10:05, 10 November 2025 (UTC) (bot has flag)
• MatrixBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 2) Approved 09:54, 10 November 2025 (UTC) (bot has flag)
• DreamRimmer bot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 4) Approved 02:04, 7 November 2025 (UTC) (bot has flag)
• TenshiBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 6) Approved 15:48, 1 November 2025 (UTC) (bot has flag)
• PhuzBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 4) Approved 15:42, 1 November 2025 (UTC) (bot has flag)
• CFA (bot) (BRFA · contribs · actions log · block log · flag log · user rights) Approved 04:31, 30 October 2025 (UTC) (bot has flag)
• ClerkBot (BRFA · contribs · actions log · block log · flag log · user rights) Approved 04:26, 30 October 2025 (UTC) (bot has flag)
• TenshiBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 7) Approved 04:10, 30 October 2025 (UTC) (bot has flag)
• DreamRimmer bot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 5) Approved 21:45, 19 October 2025 (UTC) (bot has flag)
• MilHistBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 9) Approved 11:46, 1 October 2025 (UTC) (bot has flag)
• DreamRimmer bot II (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 5) Approved 17:33, 27 September 2025 (UTC) (bot has flag)
• Monkbot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 21) Approved 17:22, 27 September 2025 (UTC) (bot has flag)
• TenshiBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 5) Approved 14:27, 27 September 2025 (UTC) (bot has flag)
• AnomieBOT (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 88) Approved 06:36, 23 September 2025 (UTC) (bot has flag)
• TenshiBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 4) Approved 06:20, 23 September 2025 (UTC) (bot has flag)
• SodiumBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 2) Approved 19:08, 14 September 2025 (UTC) (bot has flag)
• AnomieBOT (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 86) Approved 19:08, 14 September 2025 (UTC) (bot has flag)
• AnomieBOT (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 87) Approved 18:57, 14 September 2025 (UTC) (bot has flag)
• ButlerBlogBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 5) Approved 18:57, 14 September 2025 (UTC) (bot has flag)
• Blippy1998Bot (BRFA · contribs · actions log · block log · flag log · user rights) Approved 19:07, 14 September 2025 (UTC) (bot to run unflagged)
• DreamRimmer bot II (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 4) Approved 22:02, 24 August 2025 (UTC) (bot has flag)
• AnomieBOT (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 85) Approved 15:37, 22 August 2025 (UTC) (bot has flag)
• VWF bot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 2) Approved 21:06, 17 August 2025 (UTC) (bot has flag)
• CX Zoom AWB Bot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 2) Approved 06:32, 13 August 2025 (UTC) (bot has flag)
• SodiumBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 3) Approved 05:17, 12 August 2025 (UTC) (bot has flag)

Bots that have been denied for operations will be listed here for informational purposes for at least 7 days before being archived. No other action is required for these bots. Older requests can be found in the Archive.

• Grammar-FixBot (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 03:09, 29 October 2025 (UTC)

• VWF bot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 3) Bot denied 22:33, 8 October 2025 (UTC)

• MatrixBot (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 13:11, 9 August 2025 (UTC)

• Stattolinkfixerbot (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 11:31, 29 July 2025 (UTC)

• PageLinkScraper (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 07:55, 10 March 2025 (UTC)

• CiteHelperBot‬ (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 12:36, 8 January 2025 (UTC)

• MolecularBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 3) Bot denied 13:26, 1 January 2025 (UTC)

• Raph65BOT (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 00:37, 23 December 2024 (UTC)

• Silksam bot (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 12:54, 2 December 2024 (UTC)

• MdWikiBot (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 12:04, 3 August 2024 (UTC)

• Arjunaraocbot (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 07:35, 23 March 2024 (UTC)

These requests have either expired, as information required by the operator was not provided, or been withdrawn. These tasks are not authorized to run, but such lack of authorization does not necessarily follow from a finding as to merit. A bot that, having been approved for testing, was not tested by an editor, or one for which the results of testing were not posted, for example, would appear here. Bot requests should not be placed here if there is an active discussion ongoing above. Operators whose requests have expired may reactivate their requests at any time. The following list shows recent requests (if any) that have expired, listed here for informational purposes for at least 7 days before being archived. Older requests can be found in the respective archives: Expired, Withdrawn.

• Snaevar-bot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 2) Withdrawn by operator 17:33, 27 September 2025 (UTC)

• IUCNStatusBot (BRFA · contribs · actions log · block log · flag log · user rights) Expired 13:43, 24 September 2025 (UTC)

• CanonNiBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 1) Expired 18:00, 17 August 2025 (UTC)

• CFA (bot) (BRFA · contribs · actions log · block log · flag log · user rights) Expired 08:38, 3 August 2025 (UTC)

• Ow0castBot (BRFA · contribs · actions log · block log · flag log · user rights) Expired 06:50, 8 July 2025 (UTC)

• KiranBOT (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 10) Withdrawn by operator 02:59, 28 April 2025 (UTC)

• KiranBOT (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 14) Withdrawn by operator 02:54, 28 April 2025 (UTC)

• PharyngealBOT (BRFA · contribs · actions log · block log · flag log · user rights) Withdrawn by operator 03:43, 26 April 2025 (UTC)

• UrbanBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 3) Withdrawn by operator 02:21, 5 February 2025 (UTC)

• Tom.Bot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 8) Withdrawn by operator 11:37, 4 February 2025 (UTC)

• RustyBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 2) Withdrawn by operator 15:31, 1 February 2025 (UTC)

• JJPMaster (bot) (BRFA · contribs · actions log · block log · flag log · user rights) Expired 15:50, 26 January 2025 (UTC)

• BunnysBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 2) Withdrawn by operator 12:31, 13 January 2025 (UTC)

• Platybot (BRFA · contribs · actions log · block log · flag log · user rights) Expired 16:58, 12 January 2025 (UTC)

• PonoRoboT (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 2) Expired 16:53, 12 January 2025 (UTC)