Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

One Broken API Can Disrupt a Business. So I Built Something to Help.

Description and use

REBOOTX automatically detects, diagnoses, and recovers from API failures using Temporal and Gemma, reducing manual effort for small businesses.

Problem

A single API failure can halt order processing, inventory updates, and customer notifications, forcing small businesses to spend time troubleshooting instead of operating.

Outcome

REBOOTX successfully detected, diagnosed, and recovered from simulated API failures in a controlled test, demonstrating a functional incident‑to‑resolution pipeline.

Workflow

  • 1. API failure triggers webhook to REBOOTX FastAPI.
  • 2. FastAPI authenticates event via HMAC‑SHA256 and stores it in PostgreSQL with immutable audit logs.
  • 3. Transactional outbox dispatches event to Temporal workflow.
  • 4. Temporal runs IncidentRecoveryWorkflow, invoking Gemma for diagnosis.
  • 5. Gemma returns structured failure diagnosis; REBOOTX applies deterministic recovery strategy.
  • 6. Recovery worker executes safe recovery actions and verifies outcome.
  • 7. Dashboard updates with audit and recovery status.
  • 8. Operators review logs and dashboards for confirmation.

Evidence

REBOOTX detects, diagnoses, orchestrates recovery, and audits failures across connected automation engines (such as n8n).

Source

Checkpoint 3 — Google Gemma 4 AI Diagnosis: Structured failure diagnosis using gemma-4-26b-a4b-it via Google Gen AI SDK

Source

Checkpoint 2 — Temporal Recovery Orchestration: Durable Temporal workflows (IncidentRecoveryWorkflow)

Source

Simulation, test and verification report | v0.1.0 | 18 October 2026: These results gave me confidence that the core incident-to-resolution pipeline was working in the tested environment.

Source

  • Record date: 2026-10-19T01:56:14.223Z