Skip to main content
This guide helps you diagnose and resolve common issues with Heex deployments, focusing on configuration and deployment status problems.

​
Understanding Deployment Status

Systems and triggers progress through several states: 
CREATED → TO_CONFIGURE → TO_DEPLOY → DEPLOYED
  • TO_CONFIGURE: Missing required elements
  • TO_DEPLOY: Configuration complete and valid
  • DEPLOYED: Configuration deployed to edge agents (OTA) or server (historical replay)
Both edge and server deployments require the same valid configuration to reach to_deploy status.

​
System Requirements

For a system to reach to_deploy, verify:
  • Datasources: All signals used in trigger(s) exist in datasources assigned to the system
  • Triggers: At least one trigger is assigned and fully configured
  • Implementations: All required implementations are created, ready, and assigned to the system
Example: If a trigger monitors temperature and records video, you need:
  • A datasource with a temperature signal and another one (or the same) with the video signal
  • A “Temperature Monitor” implementation (ready and assigned)
  • A “Video Recorder” implementation (ready and assigned)

​
Trigger Requirements

For a trigger to reach to_deploy, verify:
  • Conditions: At least one signal condition defined (e.g., “Temperature > 30°C”)
  • Signal Validity: All signal IDs in conditions exist and are valid
  • Signal Availability: Referenced signals exist in target system datasources

​
Configuration Flow

1. Create System
   ↓
2. Create Datasource → Attach to System
   ↓
3. Create Signals → Attach to Datasource
   ↓
4. Create Implementations → Mark as Ready → Assign to System
   ↓
5. Create Trigger → Define Conditions (using Signal IDs) → Assign to System
   ↓
6. System reaches TO_DEPLOY
   ↓
7. Deploy OTA to the agent at the Edge or Server (historical replay)

​
Common Issues

​
Configuration Won’t Reach to_deploy

If your configuration is stuck in to_configure status:
  1. Check the UI for error messages - Navigate to Systems or Triggers details page for specific errors
  2. Verify implementations status - All implementations must be in ready status
  3. Validate signal IDs - Confirm all signal IDs in triggers exist and match datasource definitions
  4. Check agent connectivity - Verify the Heex Agent is installed and connected (Systems → Status tab)

​
Deployment Issues

If deployment to edge or server fails:
  1. Agent connectivity - Ensure the agent is online and connected to the cloud
  2. Network issues - Check firewall rules and network connectivity
  3. Resource constraints - Verify the target system has sufficient resources
  4. Configuration conflicts - Check for conflicting implementations or trigger conditions

​
Trigger Fires Too Frequently

Symptom: A trigger generates events constantly, overwhelming your operations team. What to Check:
  • Review event frequency for this trigger across systems
  • Check if it fires for all systems or specific units
  • Look for time-of-day patterns
Common Solutions:
  • Threshold adjustment: The current threshold may be too sensitive for normal operating conditions. If systems regularly cross the threshold under normal load, adjust the threshold to reduce false positives while maintaining safety margins.
  • Add context conditions: Consider adding additional conditions so the trigger only fires in meaningful scenarios (e.g., voltage low AND not near charging station).
  • Recording window tuning: Ensure recording windows capture enough context without excessive data storage.

​
Missing Events from Some Systems

Symptom: Several systems in your deployment haven’t generated any events over an extended period, while others generate events regularly. What to Check:
  1. Agent status: Verify the Heex agent is running on those systems and successfully connecting to your workspace
  2. Trigger assignment: Confirm triggers are assigned to those systems
  3. Signal availability: Ensure datasources for those systems contain the signals referenced by your triggers
  4. Deployment status: Check that systems have reached DEPLOYED status
Common Root Causes:
  • Agent not running or connectivity issues
  • Triggers not assigned to those specific systems
  • Missing signal definitions in datasources
  • System configuration incomplete (not all required implementations deployed)