Filedrop plugin: malformed JSON causes infinite retry loop #202

Closed
opened 2026-03-05 16:24:24 +00:00 by doxios · 1 comment
Collaborator

Bug

When a malformed JSON file is placed in the filedrop inbox, the filedrop plugin fails to parse it and retries every polling cycle indefinitely. This creates an error loop that can run for hours.

Reproduction

Place a JSON file with invalid syntax (e.g., unquoted shell expressions like $(date +%s)) in an agent's filedrop inbox.

Expected Behavior

The plugin should:

  1. Catch JSON parse errors gracefully
  2. Log a warning with the filename
  3. Move the corrupted file to a quarantine/processed directory (e.g., rename with _corrupted suffix)
  4. Continue processing remaining inbox messages

Actual Behavior

The plugin retries parsing the same corrupted file every cycle, logging the same error indefinitely.

Evidence

Corrupted file preserved at: /olymp/filedrop/Alpha/processed/1771086703_doxios_776c_corrupted.json

Alpha was stuck in this loop for hours until Zeus intervened.

## Bug When a malformed JSON file is placed in the filedrop inbox, the filedrop plugin fails to parse it and retries every polling cycle indefinitely. This creates an error loop that can run for hours. ## Reproduction Place a JSON file with invalid syntax (e.g., unquoted shell expressions like `$(date +%s)`) in an agent's filedrop inbox. ## Expected Behavior The plugin should: 1. Catch JSON parse errors gracefully 2. Log a warning with the filename 3. Move the corrupted file to a quarantine/processed directory (e.g., rename with `_corrupted` suffix) 4. Continue processing remaining inbox messages ## Actual Behavior The plugin retries parsing the same corrupted file every cycle, logging the same error indefinitely. ## Evidence Corrupted file preserved at: `/olymp/filedrop/Alpha/processed/1771086703_doxios_776c_corrupted.json` Alpha was stuck in this loop for hours until Zeus intervened.
Owner

Please create a PR for this @doxios

Please create a PR for this @doxios
k9ert closed this issue 2026-03-05 19:49:25 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ultanio/cobot#202
No description provided.