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>
Deleting a source after a successful upload first renames it to
.<name>.mhu-delete-<uuid> and then unlinks it. On a slow disk the unlink
can take several seconds. With an empty extension filter the folder
watcher and the reconcile scan reported the staged file as a new file,
so the automation queued and uploaded it again until the unlink removed
it. The jobs for the vanished staged file were then restarted by every
automatic start and skipped with "Datei nicht gefunden".
- source-cleanup-policy: shared stagedSourceName/isStagedSourceFile.
- folder-monitor and file-discovery skip staged delete files.
- Automatic starts no longer restart queue jobs that point at a staged
delete file; manual starts are unchanged.
- An ENOENT while unlinking the staged file counts as deleted instead of
a failed unlink with a restore attempt. EBUSY/EPERM keep their retries
and stay visible as failures.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With full access the installation grants every capability, destructive and
conditionally confirmed actions (queue retry/remove with source deletion,
history clear, app restart, ...) run without the local dialog, and the new
mhu_files_grant tool can add or widen directory grants. Narrowing or removing
grants and changing permissions stay local. Enabling full access in the
settings asks for local confirmation once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Automation-triggered starts and auto-retry rounds restarted every job in
error state, including files a hoster permanently rejected (e.g. Byse
"Not video file format"). Each new file in the watched folder thus
re-uploaded the rejected 3-4 GB files again on two Byse accounts.
Automatic starts now skip file-rejected jobs; manual starts still retry them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Previously sources were only removed when the whole upload batch ended. In
automation mode a batch keeps growing for hours, so hundreds of finished
files stayed on disk. A file is now removed once every required hoster
succeeded, its links are flushed to the upload log, the automation ledger
is written and the renderer confirmed the queue save. Without that evidence
the file still waits for the batch end as before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The shared upload limiter started with a full second of tokens and refilled
up to one second during short idle gaps, so new uploads could briefly send
almost twice the limit. In a parallel-upload test it released 3.87 MB in one
second at a 2 MB/s limit. Uploads now reserve send time on one shared
schedule with at most a 200 ms burst and exact waits.
Speeds and limits used 1024-based kB and MB while being shown as kB/s and
MB/s, so a limit of 100 meant 104.9 MB/s. Limits, measured speeds, ETA and
the speed graph now use 1 MB = 1,000,000 bytes. Saved limits are converted
once so the displayed value stays the same.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Address suggestions, the binding explanation and the code timestamp no longer render as separate empty-looking cards, the enable switch spans the full row, and wrapped settings dropdowns reserve room for their arrow.