Two days ago, I opened up AWB and it successfully updated to 6.4.0.0, and then worked. Today, it is back to the "Restarting in ..." (attempted save of a page in bot mode) behavior with escalating times, but with "No update available."
Description
Description
Event Timeline
Comment Actions
Ok, I got some new information while trying to save manually:
The program has encountered the following problem:
Attempted to save a wrong page (Article name: 'File:Ambox move.svg', session page title: '')
Heading: Exception in MainForm.Save
description:
workaround:
| Exception: | Exception |
|---|---|
| Message: | Attempted to save a wrong page (Article name: 'File:Ambox move.svg', session page title: '') |
| Call stack: | <pre> at AutoWikiBrowser.MainForm.Save() at AutoWikiBrowser.MainForm.btnSave_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)</pre> |
OS: Microsoft Windows NT 6.2.9200.0
version: AutoWikiBrowser (6.4.0.0), WikiFunctions (6.4.0.0), revision 12927 (2025-02-19 23:34:07)
net: 4.0.30319.42000
duplicate:
site: https://commons.wikimedia.org
AWBPlugins AWBBasePlugins - No Limits Plugin ListMakerPlugins - CategoryNoLimitsForAdminAndBotsPlugin - CategoryRecursiveNoLimitsForAdminAndBotsPlugin - CategoryRecursiveNoLimitUserDefinedLevelListProvider - ImageFileLinksNoLimitsListProvider - WhatTranscludesPageNoLimitsForAdminAndBotsPlugin - WhatTranscludesPageAllNSNoLimitsForAdminAndBotsPagePlugin - UserContribsNoLimitsForAdminAndBotsPlugin - UserContribsUserDefinedNumberForAdminAndBotsPlugin - AllPageInAllNSNLForAdminAndBotsPlugin
Comment Actions
Today, it happened again after a day or so idle, so I decided to try something different. Despite AWB showing that it was already logged in from a day or so ago, I logged it in again with Ctrl+L (using saved password but not bot password, and without closing AWB), and AWB then functioned normally. Does the system somehow "forget" that AWB was logged in, and neglect to tell AWB such that the user is prompted to login again? Perhaps the update to 6.4.0.0 (or forced updates by Windows) masked the problem (because I had to login after update anyway). I am using AWB as JeffGBot on Commons.
Comment Actions
I think when AWB is left idle for some time (not sure, many hours etc.) the edit token we got on first AWB login from the API will have expired, and either we don't get told by the API that we need a new token, or we don't handle that 'new token' message correctly. I will aim to look into it further but it may be an API-side issue that we can't resolve within AWB.
As you say what normally resolves it is to log in again, or close and reopen AWB which will mean a new log in.