Issue Summary

When a scheduled Trello automation rule is configured to move a list containing multiple cards (typically 10+ cards) from one board to another, the execution intermittently fails with a 429 LOCK_TAKEN error. Because Butler does not retry on lock errors, the list move operation decomposes into individual card moves, resulting in multiple duplicate lists of the same name being created on the destination board with cards fragmented across them.

Steps to Reproduce

1. Create two boards (e.g., Board A and Board B).
2. On Board A, create a list named "Test List" and populate it with 10–20+ cards.
3. Configure a scheduled automation rule:
   every day at <time>, move list "Test List" from board "Board A" to position 1 of board "Board B"
4. Allow the rule to trigger either via scheduled time or manual execution while other background operations/syncs are active, or trigger cross-board list moves under high card volume.

Expected Results

The entire list moves as a single unit from Board A to Board B, preserving the list structure and all cards intact in one list on the destination board.

Actual Results

The list fails to move as a unified entity. Butler encounters a lock conflict, card counts decrease incrementally, and multiple duplicate lists named "Test List" are created on Board B, leaving cards split across multiple lists and an empty list on the origin board.

The below exception is thrown in the execution logs:
 
 
 

{
  "message": "429 {\"message\":\"Unable to get locks for list move between boards\",\"error\":\"LOCK_TAKEN\"}",
  "stack": "Error: 429 {\"message\":\"Unable to get locks for list move between boards\",\"error\":\"LOCK_TAKEN\"}\n at IncomingMessage.<anonymous> (/var/task/command-queue.js:656805:25)\n at IncomingMessage.emit (node:events:531:35)\n at IncomingMessage.emit (node:domain:489:12)\n at endReadableNT (node:internal/streams/readable:1698:12)\n at process.processTicksAndRejections (node:internal/process/task_queues:89:21)"
}

Workaround

Instead of moving the entire list container between boards, keep a static list with the target name permanently created on both boards, and configure the automation rule to move the cards inside the list rather than the list itself: