ruvnet/ruflo · error

Anomaly scan error for ${deviceId}: ${error.message}

Error message

Anomaly scan error for ${deviceId}: ${error.message}

What it means

Log warning wired as onScanError in the IoT plugin's initialize: the anomaly scan worker failed while analyzing a device's vectors; that scan cycle is skipped and the anomaly-detection pipeline continues.

Source

Thrown at v3/@claude-flow/plugin-iot-cognitum/src/plugin.ts:99

      intervalMs: telemetryIntervalMs,
      onIngestionComplete: (deviceId, vectorCount) => {
        context.logger.debug(`Telemetry ingest for ${deviceId}: ${vectorCount} vectors`);
      },
      onIngestionError: (deviceId, error) => {
        context.logger.warn(`Telemetry ingest error for ${deviceId}: ${error.message}`);
      },
    });
    this.telemetryIngest.start();

    const anomalyScanIntervalMs = (config['anomalyScanIntervalMs'] as number) ?? 300_000;
    this.anomalyScan = new AnomalyScanWorker(this.coordinator, {
      intervalMs: anomalyScanIntervalMs,
      onAnomalyDetected: (deviceId, score) => {
        context.logger.warn(`Anomaly detected on ${deviceId}: trust score ${score.toFixed(3)}`);
        context.eventBus.emit('iot:anomaly-detected', { deviceId, score });
      },
      onScanError: (deviceId, error) => {
        context.logger.warn(`Anomaly scan error for ${deviceId}: ${error.message}`);
      },
    });
    this.anomalyScan.start();

    const meshSyncIntervalMs = (config['meshSyncIntervalMs'] as number) ?? 120_000;
    this.meshSync = new MeshSyncWorker(this.coordinator, {
      intervalMs: meshSyncIntervalMs,
      onMeshPartition: (deviceId, peerCount) => {
        context.logger.warn(`Mesh partition detected for ${deviceId}: ${peerCount} peers`);
        context.eventBus.emit('iot:mesh-partition', { deviceId, peerCount });
      },
      onSyncError: (deviceId, error) => {
        context.logger.warn(`Mesh sync error for ${deviceId}: ${error.message}`);
      },
    });
    this.meshSync.start();

    const firmwareWatchIntervalMs = (config['firmwareWatchIntervalMs'] as number) ?? 300_000;

View on GitHub (pinned to fa13ee4ad6)

Solutions

  1. Check the anomaly scan error detail for the device; ensure the scan model and device data are available.
Defensive patterns

Strategy: try-catch

When it happens

Trigger: Thrown at v3/@claude-flow/plugin-iot-cognitum/src/plugin.ts:99 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of ruvnet/ruflo@fa13ee4ad6 (2026-08-18). Data as JSON: /api/errors/3f8296a38f8a775c. Report an issue: GitHub.