Task #48: n8n Rebuild - Workflows From Scratch #201

New Issue

mkrause612 · 2026-03-21T02:34:07-05:00

mkrause612 commented

2026-03-21 02:34:07 -05:00

Task #48: n8n Rebuild - Workflows From Scratch

Time Estimate: 3-5 hours

Documentation: docs/tasks/ (see operations manual)

Time: 3-5 hours
Status: ACTIVE — REBUILD FROM SCRATCH (decision: March 4, 2026)
Priority: Tier 2 - Major Infrastructure
Documentation: docs/troubleshooting/n8n-node-registry-corruption.md

Rebuild n8n instance on TX1 with fresh workflows from scratch. Original workflows are considered abandoned — do not attempt to restore them.

Problem: Core nodes (HTTP Request, Execute Command) fail with "Node not found" errors due to corrupted node registry.

Decision (March 4, 2026): Rather than restoring old workflows, rebuild from scratch. Cleaner, more maintainable, aligned with current infrastructure state.

Current Workaround: PHP script (sync_codex.php) handling Codex Git sync directly. Functional but not the long-term solution.

Rebuild Procedure:

Stop n8n container
Wipe ./volumes/n8n/* directory completely
Recreate container (fresh initialization)
Verify core nodes functional (HTTP Request, Execute Command)
Rebuild workflows from scratch (do NOT re-import old JSON)
Document each new workflow as built
Test all workflows end-to-end
Re-enable scheduled executions
Monitor for 24 hours

Workflows to Rebuild (minimum):

Codex Git sync (currently handled by PHP workaround)
Discord notifications
Any other automations identified during rebuild

Prerequisites:

Maintenance window scheduled (low-traffic time)
Credentials documented before wipe
PHP workaround remains as fallback during rebuild

Post-Rebuild:

Verify Git sync workflow replaces PHP workaround
Test Discord notifications
Document all new workflows in task directory
Remove PHP workaround once n8n confirmed stable

Source: docs/core/tasks.md (Task #48)

### Task #48: n8n Rebuild - Workflows From Scratch **Time Estimate:** 3-5 hours **Documentation:** `docs/tasks/` (see operations manual) --- **Time:** 3-5 hours **Status:** ACTIVE — REBUILD FROM SCRATCH (decision: March 4, 2026) **Priority:** Tier 2 - Major Infrastructure **Documentation:** `docs/troubleshooting/n8n-node-registry-corruption.md` Rebuild n8n instance on TX1 with fresh workflows from scratch. Original workflows are considered abandoned — do not attempt to restore them. **Problem:** Core nodes (HTTP Request, Execute Command) fail with "Node not found" errors due to corrupted node registry. **Decision (March 4, 2026):** Rather than restoring old workflows, rebuild from scratch. Cleaner, more maintainable, aligned with current infrastructure state. **Current Workaround:** PHP script (`sync_codex.php`) handling Codex Git sync directly. Functional but not the long-term solution. **Rebuild Procedure:** 1. Stop n8n container 2. Wipe `./volumes/n8n/*` directory completely 3. Recreate container (fresh initialization) 4. Verify core nodes functional (HTTP Request, Execute Command) 5. Rebuild workflows from scratch (do NOT re-import old JSON) 6. Document each new workflow as built 7. Test all workflows end-to-end 8. Re-enable scheduled executions 9. Monitor for 24 hours **Workflows to Rebuild (minimum):** - Codex Git sync (currently handled by PHP workaround) - Discord notifications - Any other automations identified during rebuild **Prerequisites:** - Maintenance window scheduled (low-traffic time) - Credentials documented before wipe - PHP workaround remains as fallback during rebuild **Post-Rebuild:** - Verify Git sync workflow replaces PHP workaround - Test Discord notifications - Document all new workflows in task directory - Remove PHP workaround once n8n confirmed stable --- --- **Source:** `docs/core/tasks.md` (Task #48)

mkrause612 added the

area/automation for/michael labels 2026-03-21 02:34:07 -05:00

mkrause612 commented

2026-04-01 18:16:15 -05:00

This issue is being closed as part of the task system migration on April 1, 2026.

Why: The Gitea Issues + Kanban approach proved too heavyweight for daily operations and lacked accessibility for non-technical team members (Meg, Holly).

New System:

BLOCKERS.md - Critical soft launch tasks
BACKLOG.md - Future work organized by theme
Trinity Console v2 Task Module (planned) - Web-based task management

Archive: All issues preserved in docs/archive/gitea-issues-archive-2026-04-01.md

— Chronicler #54

This issue is being closed as part of the task system migration on April 1, 2026. **Why:** The Gitea Issues + Kanban approach proved too heavyweight for daily operations and lacked accessibility for non-technical team members (Meg, Holly). **New System:** - `BLOCKERS.md` - Critical soft launch tasks - `BACKLOG.md` - Future work organized by theme - Trinity Console v2 Task Module (planned) - Web-based task management **Archive:** All issues preserved in `docs/archive/gitea-issues-archive-2026-04-01.md` — Chronicler #54

mkrause612 closed this issue

2026-04-01 18:16:15 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: firefrost-gaming/firefrost-operations-manual#201