jackwener/OpenCLI · error · CommandExecutionError

Instagram private publish configure_sidecar failed: ${respon

Error message

Instagram private publish configure_sidecar failed: ${response.status}${detail}

What it means

After parsing, publishSidecarWithRetry checks response.ok. When configure_sidecar returns a non-2xx status the library throws this error, appending the HTTP status and the first 500 chars of the response body as detail. It means Instagram itself rejected the sidecar configuration request at the HTTP level.

Source

Thrown at clis/instagram/_shared/private-publish.js:858

        headers: {
            ...buildPrivateApiHeaders(input.apiContext),
            'Content-Type': 'application/json',
        },
        body: JSON.stringify(input.payload),
    };
    for (let attempt = 0; attempt < INSTAGRAM_PRIVATE_SIDECAR_TRANSCODE_ATTEMPTS; attempt += 1) {
        const response = await input.fetcher('https://www.instagram.com/api/v1/media/configure_sidecar/', requestInit);
        const text = await response.text();
        let json = {};
        try {
            json = text ? JSON.parse(text) : {};
        }
        catch {
            throw new CommandExecutionError('Instagram private publish configure_sidecar returned invalid JSON');
        }
        if (!response.ok) {
            const detail = text ? ` ${text.slice(0, 500)}` : '';
            throw new CommandExecutionError(`Instagram private publish configure_sidecar failed: ${response.status}${detail}`);
        }
        const message = String(json?.message || '');
        if (response.status === 202
            || /transcode not finished yet/i.test(message)) {
            if (attempt >= INSTAGRAM_PRIVATE_SIDECAR_TRANSCODE_ATTEMPTS - 1) {
                throw new CommandExecutionError('Instagram private publish configure_sidecar timed out waiting for video transcode', text.slice(0, 500));
            }
            await waitMs(INSTAGRAM_PRIVATE_SIDECAR_TRANSCODE_WAIT_MS);
            continue;
        }
        if (String(json?.status || '').toLowerCase() === 'fail') {
            throw new CommandExecutionError('Instagram private publish configure_sidecar failed', message || text.slice(0, 500));
        }
        return { code: json?.media?.code };
    }
    throw new CommandExecutionError('Instagram private publish configure_sidecar failed');
}
export async function publishMediaViaPrivateApi(input) {

View on GitHub (pinned to 49907e53dc)

Solutions

  1. Read the embedded status and body detail in the message to identify the exact failure (403 → auth, 429 → rate limit, 400 → payload).
  2. Refresh csrfToken and session cookies if the status is 401/403.
  3. Back off and wait if the status is 429; reduce publish frequency.
  4. Validate the payload built by buildConfigureSidecarPayload (uploadIds, caption, clientSidecarId, jazoest) if the status is 400.
  5. Retry on 5xx; these are usually transient Instagram-side failures.

Example fix

// before
await publishMediaViaPrivateApi({ mediaItems, apiContext });
// after
try {
  await publishMediaViaPrivateApi({ mediaItems, apiContext });
} catch (e) {
  if (/failed: 429/.test(e.message)) await new Promise(r => setTimeout(r, 60000));
  throw e;
}
Defensive patterns

Strategy: try-catch

Validate before calling

// Validate API context before calling
if (!apiContext.csrfToken) throw new Error('Missing csrfToken — configure_sidecar would 403');

Type guard

function hasValidApiContext(ctx) {
  return typeof ctx?.csrfToken === 'string' && ctx.csrfToken.length > 0;
}

Try / catch

try {
  await publishMediaViaPrivateApi({ mediaItems, apiContext });
} catch (e) {
  const m = /failed: (\d{3})/.exec(e.message);
  if (m && m[1] === '429') await sleep(60000);
  if (m && (m[1] === '401' || m[1] === '403')) await refreshSession(page);
  throw e;
}

Prevention

When it happens

Trigger: POST to /api/v1/media/configure_sidecar/ returns any non-OK HTTP status (400 bad payload, 401/403 auth, 429 rate-limited, 5xx server error), with the status and body detail embedded in the message.

Common situations: Malformed sidecar payload (bad upload ids or jazoest) causing 400; expired CSRF token causing 403; too many publishes triggering 429; Instagram API downtime producing 5xx.

Understand the failure class

Background: "API error: {status}" and "HTTP 401/403/404/429/5xx" errors: non-2xx HTTP responses explained — this error's family across 27 libraries.

Related errors

AI-assisted analysis of jackwener/OpenCLI@49907e53dc (2026-08-29). Data as JSON: /api/errors/1e0627e479343eb7. Report an issue: GitHub.