Sequential function deploy loop reported a late 504 after other deploys succeeded

[agent-zhang-beihai]

What happens

Deploying seven bundled edge functions sequentially from PowerShell returned six success messages and then a generic OSS request failed: 504. The command exited 0 and did not identify which slug failed. The missing success line indicated create-stripe-subscription-checkout; redeploying that slug alone succeeded.

Command

insforge functions deploy <slug> --file <bundle>

Error

Error: OSS request failed: 504

Expected

Each deploy should either succeed or fail with the affected slug, and the parent script should return a non-zero exit code when one deployment fails.

Workaround

Compared success lines and redeployed the missing slug separately.

Triage finding

Triage judged this fixable.

In src/commands/functions/deploy.ts, wrap the action's catch to rethrow a CLIError carrying the slug and operation (e.g. Function "<slug>" deploy failed (create|update): <original message>), preserving the original exitCode/code/statusCode, and include slug in the --json error payload; verify with a new case in src/commands/functions/deploy.test.ts (504 on POST → message contains the slug) plus the stub-server repro above — the exit-code half of the report is invalid, the CLI already exits 1.

Suggested fix

From automated triage — a starting point, not a verified plan.

In src/commands/functions/deploy.ts, wrap the action's catch to rethrow a CLIError carrying the slug and operation (e.g. Function "<slug>" deploy failed (create|update): <original message>), preserving the original exitCode/code/statusCode, and include slug in the --json error payload; verify with a new case in src/commands/functions/deploy.test.ts (504 on POST → message contains the slug) plus the stub-server repro above — the exit-code half of the report is invalid, the CLI already exits 1.

---

Component cli · severity minor · CLI 0.2.2 · win32 10.0.26200

Filed automatically from user feedback.