Lucas Berger
07aeace1fd
- Fix update sub-workflow: remove unsupported GraphQL filter arg, fix node reference (Format Pull Error → Format Update Error), fix field case (data.image → data.Image) - Fix batch cancel: connect Route Callback output 20 (batchcancel) to Prepare Batch UI Input (was empty connection array) - Fix text commands: change .item.json to .first().json for paired item breakage after GraphQL chain expansion; convert Send Batch Confirmation from Telegram node to HTTP Request to fix double-serialized reply_markup Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
68 lines
3.7 KiB
Markdown
68 lines
3.7 KiB
Markdown
---
|
|
status: verifying
|
|
trigger: "The cancel button on the batch confirmation dialog does not work"
|
|
created: 2026-02-09T00:00:00Z
|
|
updated: 2026-02-09T00:02:00Z
|
|
---
|
|
|
|
## Current Focus
|
|
|
|
hypothesis: CONFIRMED - Route Callback output index 20 (batchcancel) had empty connection array
|
|
test: fix applied and pushed to n8n (HTTP 200)
|
|
expecting: batch cancel button now routes to Prepare Batch UI Input -> Batch UI sub-workflow -> Handle Cancel
|
|
next_action: user verification - press cancel button on batch confirmation dialog in Telegram
|
|
|
|
## Symptoms
|
|
|
|
expected: Cancel button on batch confirmation dialog should cancel the operation and return user to previous state
|
|
actual: Cancel button does nothing (callback is parsed but routed to empty connection)
|
|
errors: No error in n8n - execution silently ends because route goes nowhere
|
|
reproduction: select containers in batch, confirm selection, press cancel on confirmation dialog
|
|
started: after Phase 16 migration (Docker socket proxy -> Unraid GraphQL API)
|
|
|
|
## Eliminated
|
|
|
|
## Evidence
|
|
|
|
- timestamp: 2026-02-09T00:00:30Z
|
|
checked: Parse Callback Data node in n8n-workflow.json (line 558)
|
|
found: batch:cancel callback is correctly parsed, sets isBatchCancel=true
|
|
implication: callback parsing is working correctly
|
|
|
|
- timestamp: 2026-02-09T00:00:40Z
|
|
checked: Route Callback switch node outputs (lines 569-1094)
|
|
found: isBatchCancel is output index 20 (outputKey "batchcancel"), the LAST output
|
|
implication: routing rule exists and should match correctly
|
|
|
|
- timestamp: 2026-02-09T00:00:50Z
|
|
checked: Route Callback connection array (lines 5495-5638)
|
|
found: Output index 20 is empty array [] (line 5637) while outputs 14-19 all connect to "Prepare Batch UI Input"
|
|
implication: ROOT CAUSE - batch:cancel callback is parsed and routed but the output goes nowhere
|
|
|
|
- timestamp: 2026-02-09T00:00:55Z
|
|
checked: Prepare Batch UI Input node (line 3420)
|
|
found: Node explicitly handles isBatchCancel -> sets action='cancel', and Batch UI sub-workflow has cancel route
|
|
implication: The downstream handling exists and is correct - only the connection is missing
|
|
|
|
- timestamp: 2026-02-09T00:01:00Z
|
|
checked: Batch UI sub-workflow cancel route (n8n-batch-ui.json line 564-576)
|
|
found: Handle Cancel node returns {action:'cancel', chatId, messageId, queryId, answerText:'Batch selection cancelled'}
|
|
implication: Sub-workflow cancel handling is complete - just needs to be reached
|
|
|
|
- timestamp: 2026-02-09T00:01:00Z
|
|
checked: batch:cancel callback sources
|
|
found: Used in 3 places: (1) batch selection UI cancel button, (2) batch stop confirmation cancel button, (3) text-command batch confirmation cancel button
|
|
implication: This broken connection affects ALL batch cancel scenarios, not just one dialog
|
|
|
|
- timestamp: 2026-02-09T00:02:00Z
|
|
checked: Fix applied - connected output 20 to "Prepare Batch UI Input"
|
|
found: JSON validated, workflow pushed to n8n successfully (HTTP 200)
|
|
implication: Fix is deployed - needs user verification via Telegram
|
|
|
|
## Resolution
|
|
|
|
root_cause: Route Callback switch node output index 20 (batchcancel) had empty connection array [] instead of connecting to "Prepare Batch UI Input" like all other batch-related outputs (indices 14-19). This was likely a wiring oversight during Phase 16 migration when batch operations were added to the Route Callback switch - the batchcancel rule was added last but its connection was left empty.
|
|
fix: Connected Route Callback output index 20 (batchcancel) to "Prepare Batch UI Input" node, matching the pattern of outputs 14-19 (bexecTextCmd, batchmode, batchtoggle, batchnav, batchexec, batchclear)
|
|
verification: Fix applied and pushed to n8n (HTTP 200). JSON validated. Awaiting user Telegram verification.
|
|
files_changed: [n8n-workflow.json]
|