How do I enable or disable an entire AutoConfig job in Gunbot?

Gunbot's AutoConfig lets you define multiple automated jobs with their own schedules and filters. If you want to pause a job without deleting it (or keep a new job inactive until ready), use the enabled parameter.

Use the AutoConfig wizard

Nearly every option that follows can be set without editing files by hand.
Click the ⋮ (three-dots) menu ➜ AutoConfig, step through the wizard, and press Save; it will write a correct autoconfig.json for you.

The enabled Parameter: Simple Job Control

The enabled parameter is a boolean flag (true or false) you can include in each AutoConfig job definition in autoconfig.json.

• "enabled": true: The job is active and runs according to its schedule. This is the default if enabled is omitted and the job parses successfully.
• "enabled": false: The job is inactive. Gunbot keeps the configuration but does not schedule or run it.

How to Use the enabled Parameter

Add the enabled parameter at the top level of a specific job’s configuration block.

Consider the following autoconfig.json snippet with two jobs:

{
  "dailyVolumeScanner": {
    "enabled": true, // This job is active
    "type": "addPairs",
    "schedule": "0 1 * * *", // Runs daily at 1 AM
    "pairs": {
      "exchange": "binance",
      "include": "USDT-"
    },
    // ... other settings for dailyVolumeScanner
  },
  "experimentalTrendFilter": {
    "enabled": false, // This job is currently disabled
    "type": "manageOverrides",
    "schedule": "*/30 * * * *", // Would run every 30 mins if enabled
    "pairs": {
      "exchange": "kraken",
      "include": "USDT-BTC,USDT-ETH"
    },
    // ... other settings for experimentalTrendFilter
  }
}

In this example:

• dailyVolumeScanner will run as scheduled because "enabled": true.
• experimentalTrendFilter will not run, even though it has a valid schedule and configuration, because "enabled": false. Its settings are preserved, but Gunbot's AutoConfig module will skip its execution.

To activate experimentalTrendFilter, change its enabled value to true and let Gunbot reload autoconfig.json (it usually does this automatically on change, or after a restart).

Benefits of Using enabled

1. Safe testing: Set "enabled": false on a new job while you refine filters, overrides, and schedules. Flip to true when ready.
2. Temporary deactivation: Pause a strategy for market conditions or maintenance without losing configuration.
3. Preserving configurations: Keep complex jobs for later use instead of deleting them.
4. Conditional or seasonal jobs: Keep event-driven jobs configured but inactive until needed.
5. Reducing system load: Disable non-critical jobs to free resources and isolate performance issues.
6. Manual A/B testing: Enable one of two similar jobs to compare behavior over time.

Reloading Configuration

When you change the enabled status (or anything else in autoconfig.json), Gunbot must reload the file. Gunbot typically watches autoconfig.json and reloads automatically. If changes do not take effect, restart Gunbot to load the latest configuration.

The enabled parameter is a non-destructive way to control which AutoConfig jobs run. Review enabled status regularly to ensure only intended automations are active.