Retry DoodStream upload-page server errors as transient
A single HTTP 500 from the DoodStream upload page while resolving the upload session was reported as "sess_id nicht gefunden nach Login". That message matched the session cooldown pattern, so the job failed at once without a retry and the account was paused. - 5xx and 408 answers of the upload page throw "DoodStream: Upload-Seite antwortete mit HTTP <status>" flagged transientNetwork. The existing upload-manager loop retries on the same account up to the configured retries and does not pause the account. - Other non-200 answers name the status and keep the session renewal path (account cooldown, new login). - HTTP 200 without sess_id keeps the session error. - English translation for the new message. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
23fc22fd7d
commit
abc801e60c
2 files changed
+7
No files matched your search
@@ -232,6 +232,12 @@ class DoodstreamUploader {
|
||||
this.sessId = '';
|
||||
const guest = /utype\s*:\s*['"]anon['"]/.test(html);
|
||||
_debugLog(`session-missing HTTP=${res.status} guest=${guest} cookies=${this.cookies.size}`, true);
|
||||
if (res.status !== 200) {
|
||||
const error = new Error(`DoodStream: Upload-Seite antwortete mit HTTP ${res.status}`);
|
||||
if (res.status >= 500 || res.status === 408) error.transientNetwork = true;
|
||||
else error.accountError = true;
|
||||
throw error;
|
||||
}
|
||||
throw new Error('Doodstream: sess_id nicht gefunden nach Login');
|
||||
}
|
||||
|
||||
|
||||
Reference in new issue
Block a user