You can stop the bot by pushing the stop button. The bot sees and immediately stops running. Unless it is an emergency please consider reporting problems first to the talk page.

@Cyberpower678 and Dweller: .. thinking about setting the fuse for once a month around 00:30 GMT starting tomorrow. -- GreenC 15:26, 19 September 2017 (UTC)[reply]

You should be careful about this. Check to make sure your previous bot jobs are finished before firing off another job.—CYBERPOWER (Chat) 15:43, 19 September 2017 (UTC)[reply]

It could easily but didn't imagine the job might still be active after 30 days.. -- GreenC 16:58, 19 September 2017 (UTC)[reply]

Considering the importance, I would think weekly is better.—CYBERPOWER (Chat) 17:16, 19 September 2017 (UTC)[reply]

Ok, doesn't matter to me. Will wait to see if Dweller has any thought. -- GreenC 17:48, 19 September 2017 (UTC)[reply]

@Cyberpower678: It appears we may not be hearing from Dweller possibly ever again though I hope not the case. -- GreenC 17:33, 20 September 2017 (UTC)[reply]

I left him a note. Sadly enough, I inadvertently copy and pasted some IABot code in the edit summary. :/—CYBERPOWER (Chat) 17:42, 20 September 2017 (UTC)[reply]

Ok. I left a note with user Dank as I'm hesitant to run without support from the FA community as noted in the BRFA. -- GreenC 17:53, 20 September 2017 (UTC)[reply]

Dank is now contact the bot will run at 4:37am GMT Thursday. -- GreenC 19:41, 20 September 2017 (UTC)[reply]

User:Cyberpower678 -- Job 907 took more than 7 days to complete (by about 3 hours) so the next batch aborted startup since the first was still running. Is this because the database was down during the last week, or should I increase the number of days between runs? -- GreenC 14:54, 3 November 2017 (UTC)[reply]

The new version 1.6 of IABot has the impressive ability to detect reverts. Unfortunately, it's also caused massive spikes in memory consumption. This caused crashes and spikes in DB connections, which crashed the DB.—CYBERPOWER (Chat) 16:33, 3 November 2017 (UTC)[reply]

Ok no problem, glad you got a handle on the issues. For monitoring system resources on unix try vmstat 1. At least you wrote the app and know the source, usually with sysadmin issues it's a black box what the app is doing. I've moved the bot up a day so it will start early sat morning. -- GreenC 21:25, 3 November 2017 (UTC)[reply]

Hello, I am just dropping by to let you know that when watching the interface log on the IABot management interface I noticed that the bot this bot was submitting empty jobs. The jobs since 2 June 2018 have all been empty. However this may actually be a problem with the IABot interface since user submitted jobs have also been having problems. Not sure if its worth running the bot when it can't do its job? Thanks. Redalert2fan (talk) 16:23, 23 June 2018 (UTC)[reply]

Edit: I see there is already a task posted on phabricator. Redalert2fan (talk) 16:28, 23 June 2018 (UTC)[reply]

User:Redalert2fan. That was me testing. Opened T198016 - I'll add a note other user submitted jobs are also not working. -- GreenC 16:53, 23 June 2018 (UTC)[reply]

Just a note for if you haven't seen it on phabricator yet, submitting bot jobs is possible and working again. Redalert2fan (talk) 05:27, 22 July 2018 (UTC)[reply]