Goal Statuses Explained (Active / Completed / Archived)

Modified on Mon, 17 Nov at 10:22 PM

Goal Statuses Explained (Active / Completed / Archived)

Overview

Every goal in ARMOR has a status that determines whether it's actively monitoring your fleet, temporarily paused, or archived for historical reference. Understanding these statuses helps you manage your goals effectively and keeps your Goal Management dashboard organized.

This guide explains each status, how to change between them, and when to use each one.

The Three Goal Statuses

1. Active

✅ Active goals are running and monitoring your fleet.

ARMOR checks these goals according to their schedule (daily, weekly, or monthly) and generates alerts when thresholds are crossed.

Characteristics:

  • Appears in the main Goal Management list
  • Checks run automatically on schedule
  • Alerts are generated and notifications sent
  • Visible on asset detail pages and dashboards
  • Can be edited at any time

When to use:

  • Goals you're actively monitoring
  • Production goals that drive operational decisions
  • New goals being tested in pilot phase

2. Inactive (Paused)

⏸️ Inactive goals are paused but not deleted.

ARMOR retains the goal configuration but does not run checks or generate alerts. Easily reactivated when needed.

Characteristics:

  • Still appears in Goal Management list (with "Inactive" badge)
  • Checks do NOT run
  • Alerts are NOT generated
  • Configuration is preserved
  • Can be reactivated with one click
  • Can still be edited

When to use:

  • Seasonal goals (e.g., winter operations only)
  • Goals being tested before full deployment
  • Temporarily pausing alerts during maintenance periods
  • Goals that need threshold adjustments before resuming

3. Archived

? Archived goals are removed from active view but retained for historical reference.

Used for goals that are no longer relevant but shouldn't be deleted (for audit or reporting purposes).

Characteristics:

  • Hidden from main Goal Management list by default
  • Checks do NOT run
  • Alerts are NOT generated
  • Historical data is preserved
  • Can be viewed with "Show Archived" filter
  • Cannot be reactivated without un-archiving first

When to use:

  • Completed pilot projects
  • Goals replaced by newer versions
  • Equipment that's been retired or sold
  • Goals no longer aligned with current operations
  • Historical record-keeping

Status Lifecycle Diagram

Typical Goal Lifecycle:

[Create Goal] → Active
↓ (pause temporarily)
Inactive
↓ (reactivate)
Active
↓ (no longer needed)
Archived

How to Change Goal Status

Activating a Goal

From Goal Editor:

  1. Open the goal in edit mode
  2. Locate the "Active" toggle at the top of the form
  3. Turn the toggle ON (green)
  4. Click "Save Goal"

From Goal Management List:

  1. Find the goal (may need to enable "Show Inactive")
  2. Click the three-dot menu (⋮)
  3. Select "Activate"

Effect: Goal immediately begins running on its next scheduled check.

Deactivating (Pausing) a Goal

From Goal Editor:

  1. Open the goal in edit mode
  2. Locate the "Active" toggle
  3. Turn the toggle OFF (gray)
  4. Click "Save Goal"

From Goal Management List:

  1. Find the active goal
  2. Click the three-dot menu (⋮)
  3. Select "Deactivate"

Effect: Goal stops running immediately. No new checks or alerts are generated.

Archiving a Goal

From Goal Management List:

  1. Find the goal (must be Inactive first - deactivate if needed)
  2. Click the three-dot menu (⋮)
  3. Select "Archive"
  4. Confirm the archive action

Effect: Goal is hidden from the main list and marked as archived. Can be viewed with "Show Archived" filter.

⚠️ Note: You cannot archive an Active goal. First deactivate it, then archive.

Un-archiving a Goal

From Goal Management List:

  1. Enable the "Show Archived" filter
  2. Find the archived goal
  3. Click the three-dot menu (⋮)
  4. Select "Unarchive"

Effect: Goal returns to Inactive status. Still needs to be manually activated to resume monitoring.

Status Comparison Table

Feature Active Inactive Archived
Visible in main list ✅ Yes ✅ Yes ❌ No (filter required)
Runs scheduled checks ✅ Yes ❌ No ❌ No
Generates alerts ✅ Yes ❌ No ❌ No
Can be edited ✅ Yes ✅ Yes ⚠️ Must unarchive first
Shows on asset pages ✅ Yes ❌ No ❌ No
Quick reactivation N/A ✅ One click ⚠️ Unarchive, then activate
Historical data retained ✅ Yes ✅ Yes ✅ Yes

Common Use Cases

Use Case 1: Seasonal Goals

Scenario: You monitor heating runtime in winter, cooling runtime in summer.

Status management:

  • Winter: Heating goal is Active, cooling goal is Inactive
  • Spring: Deactivate heating goal, activate cooling goal
  • Fall: Deactivate cooling goal, reactivate heating goal

Keep both goals in the system year-round, toggling status as seasons change.

Use Case 2: Testing New Thresholds

Scenario: You want to test a stricter threshold without affecting the production goal.

Status management:

  1. Keep original goal Active
  2. Create a duplicate goal with stricter threshold
  3. Set the duplicate to Inactive initially
  4. Activate the duplicate for 1-2 weeks to test
  5. If successful, deactivate the original and keep the new one active
  6. Archive the original goal for reference

Use Case 3: Fleet Changes

Scenario: You retire a group of assets and replace them with new equipment.

Status management:

  • Goals tied to old assets → Deactivate, then Archive
  • Create new goals for replacement equipment → Active
  • Keep archived goals for historical reporting

Use Case 4: Pilot to Production

Scenario: You tested a goal on 5 assets, now rolling out fleet-wide.

Status management:

  1. Pilot goal (5 assets) → Keep Active temporarily
  2. Create fleet-wide goal with same settings
  3. Set fleet-wide goal to Active
  4. Monitor both for 1 week to confirm consistency
  5. Deactivate pilot goal
  6. Archive pilot goal after 30 days

Best Practices

  • Use Inactive for temporary pauses - Don't archive goals you'll need again soon
  • Archive instead of delete - Retain goals for historical reference and audit trails
  • Clean up quarterly - Review inactive goals every 90 days and archive those no longer needed
  • Document reasons - When archiving, note why in the goal description (e.g., "Replaced by Goal #245")
  • Test before activating - Create new goals as Inactive first, review settings, then activate
  • Communicate changes - Let your team know when goals are activated or deactivated

Filtering by Status

In Goal Management

Use the filter options at the top of the Goal Management page:

  • Show All - Active and Inactive goals (default view)
  • Show Active Only - Only goals currently monitoring
  • Show Inactive Only - Only paused goals
  • Show Archived - View archived goals (hidden by default)

Status Indicators

Goals in the list show status badges:

  • ✅ Green badge: Active
  • ⏸️ Gray badge: Inactive
  • ? Light gray badge: Archived (when "Show Archived" enabled)

Troubleshooting Status Issues

Goal Shows as Active but Not Generating Alerts

Possible causes:

  • Threshold is too lenient (all assets meeting it)
  • Scope is empty (no assets selected)
  • Check schedule hasn't occurred yet

Solution: Verify the goal status is truly Active (green toggle). Check scope settings. Review threshold values. Wait for next scheduled check.

Cannot Archive a Goal

Possible causes:

  • Goal is currently Active (must deactivate first)

Solution: Open the goal, turn off the Active toggle, save, then archive.

Archived Goal Still Generating Alerts

Possible causes:

  • Goal wasn't properly archived (check status in filtered list)
  • Alerts are from a different goal with similar name

Solution: Enable "Show Archived" filter and confirm goal status. Check alert details to identify which goal triggered it.

Related Topics

Getting Help

If you need assistance with goal statuses or lifecycle management, contact the ARMOR Support Team.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article