WF4S: All Puppeteer endpoints target wrong container

[mark-bfd]

Summary

WF4S-Production v41 targets pr_alpha_puppeteer_visual (aggregated chain container) instead of pr_alpha_puppeteer_single (S-Chain container) in ALL 4 Puppeteer-related operations.

Severity

CRITICAL - Entire WF4S workflow may be non-functional

Affected Nodes

1. Check Puppeteer Health - http://pr_alpha_puppeteer_visual:3100/health
2. Check Queue Status - http://pr_alpha_puppeteer_visual:3100/queue-status
3. Run Puppeteer Automation - http://pr_alpha_puppeteer_visual:3100/automation
4. Restart Puppeteer Container - docker restart pr_alpha_puppeteer_visual

Expected Configuration

All should target pr_alpha_puppeteer_single:

• Health: http://pr_alpha_puppeteer_single:3100/health
• Queue: http://pr_alpha_puppeteer_single:3100/queue-status
• Automation: http://pr_alpha_puppeteer_single:3100/automation
• Restart: docker restart pr_alpha_puppeteer_single

Impact

• S-Chain single-PR payloads sent to A-Chain aggregated container
• Health checks monitoring wrong container
• Recovery mechanism (restart) targets wrong container
• Queue management checking wrong instance

Root Cause

Likely copy-paste from WF4A (A-Chain) workflow without find/replace.

Fix

Single find/replace in WF4S-Production.json:

Find:    pr_alpha_puppeteer_visual
Replace: pr_alpha_puppeteer_single

Chain

S-Chain (Single PR Processing)

Workflow

WF4S-Production v41

[github-actions[bot]]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.