NousResearch/hermes-agent · error

result.confirm_message?.trim() || translateNow('cron.modelIm

Error message

result.confirm_message?.trim() || translateNow('cron.modelImpact.saveFailed')

What it means

Error "result.confirm_message?.trim() || translateNow('cron.modelImpact.saveFailed')" thrown in NousResearch/hermes-agent.

Source

Thrown at apps/desktop/src/store/cron-model-impact.ts:155

      label: translateNow('cron.modelImpact.review'),
      onClick: () => {
        if (currentActionScope(profile, connection)) {
          requestCronReview()
        }
      }
    }
  })
}

export async function setMainModelAssignment(
  request: Omit<ModelAssignmentRequest, 'scope'>
): Promise<ModelAssignmentResponse> {
  const { connection, generation } = beginCronModelImpactAssignment()
  const profile = profileIdentity()
  const result = await setModelAssignment({ ...request, scope: 'main' })

  if (result.ok !== true) {
    throw new Error(result.confirm_message?.trim() || translateNow('cron.modelImpact.saveFailed'))
  }

  if (!currentResponseScope(profile, connection, generation)) {
    return result
  }

  // Missing means an older backend. It is not evidence that an existing impact
  // has gone away, so leave the current warning untouched.
  if (result.cron_model_impact !== undefined) {
    const impact = parseCronModelImpact(result.cron_model_impact)

    if (impact) {
      publishImpact(impact, profile, connection, generation)
    }
  }

  return result
}

View on GitHub (pinned to c896c09c42)

Solutions

  1. Review the save error returned by the gateway and retry.
  2. Verify the cron job fields are valid before saving the model-impact change.

When it happens

Trigger: Thrown at apps/desktop/src/store/cron-model-impact.ts:155 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of NousResearch/hermes-agent@c896c09c42 (2026-08-14). Data as JSON: /api/errors/53265b119d0c905e. Report an issue: GitHub.