jackwener/OpenCLI · warning

Could not restore Midjourney video defaults: ${message}

Error message

Could not restore Midjourney video defaults: ${message}

What it means

After a Midjourney video job, the CLI tries to restore the account-wide video settings to their defaults. If restoration fails but the job itself already succeeded (a childId or primary error exists), it warns instead of failing the command, since throwing would push users into accidentally submitting a duplicate paid job.

Source

Thrown at clis/midjourney/action.js:378

          Math.min(timeout, 90),
          submittedAt,
        );
      }
    } catch (error) {
      primaryError = error;
      throw error;
    } finally {
      // Video actions temporarily mutate account-wide defaults. Always put
      // them back, including when preparation, submission, or correlation fails.
      try {
        await restoreVideoSettings(page, originalSettings, changedResolution, changedBatch);
      } catch (error) {
        const message = error instanceof Error ? error.message : String(error);
        // Once a paid child id is known, surfacing restoration as command
        // failure would encourage an accidental duplicate. Preserve the job
        // result and make the account-wide setting risk explicit instead.
        if (childId || primaryError) {
          log.warn(`Could not restore Midjourney video defaults: ${message}`);
        } else {
          throw error;
        }
      }
    }
    if (!normalizeBoolean(kwargs.wait, true)) {
      const afterSubmit = await getMidjourneyAccount(page);
      await recordQuotaSnapshot(afterSubmit, 'action-after-submit');
      return [actionResult(source, operation, estimated, {
        jobId: childId,
        status: 'submitted',
        observedMinutes: observedMinutes(account, afterSubmit),
        index: index[0] + 1,
        url: jobUrl(childId),
      })];
    }

    const elapsedSeconds = (Date.now() - submittedAt) / 1000;

View on GitHub (pinned to 49907e53dc)

Solutions

1. Treat the warning as informational: the paid job result was preserved, so do NOT resubmit the job
2. Verify the account's video settings on the Midjourney website and reset them manually if needed
3. Re-authenticate the Midjourney session if the message indicates auth problems
4. Rerun only the settings restoration (e.g., a settings/defaults command) rather than the whole video job

Example fix

// before
// $ opencli midjourney video ...  # job succeeded but settings left customized
// after: manually verify/reset
// Midjourney settings -> video defaults restored; no duplicate job submitted

// confirm job succeeded before ever resubmitting
const job = await getMidjourneyJob(childId);
if (job?.status !== 'succeeded') throw new Error('Job not confirmed; investigate before rerun');

try { await restoreVideoDefaults(); }
catch (e) { log.warn(`restore failed: ${e.message}`); /* keep job result */ }

When it happens

Trigger: The video generation completed and a child job id exists, but the subsequent call to reset Midjourney video defaults (via the web session) threw an error.

Common situations: Midjourney session expired or got logged out between job submission and restoration, transient network failure on the settings request, Midjourney UI/API change breaking the settings-reset flow, rate limiting on the account.

Related errors

• --repeat must be a positive integer
• operation must be one of: ${ACTION_CHOICES.join(', ')}
• No cost model is defined for action "${operation}"
• ${capabilities.plan || 'current'} plan does not support HD v
• describe currently requires a local image file

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