JustFlows docs

Guide

System health

The admin dashboard and System Health page summarize the application, scheduler heartbeat, queue, cache, storage, logs, and runtime versions.

Operational widgets also surface workflow reliability, failure hotspots, AI usage, Flowy diagnostics, and subscription activity.

When a customer reports a stuck or failed workflow, check in this order:

  1. the flow is published and its trigger is active;
  2. the workspace still has plan access and remaining usage;
  3. the scheduler heartbeat is healthy and the queue worker process is running in Supervisor, Docker, systemd, or the equivalent service manager;
  4. the required workspace integration or AI account still validates;
  5. the run's last node and error details;
  6. storage/logs/laravel.log and relevant provider/payment logs.

System Health shows observable queue activity, backlog, and failed jobs, but an idle queue cannot prove that a worker is running. Monitor the queue backlog, failed jobs, disk/database growth, external API failures, payment webhook delivery, SSL expiry, and backup age. Configure external uptime monitoring for both the public site and a workflow smoke test.