Manage pair lists with 'pairs.removeDisabled' in AutoConfig

Gunbot's AutoConfig removePairs job type is primarily used to automatically delist pairs based on dynamic filter conditions like low profit or volume. However, it also offers an auxiliary function through the pairs.removeDisabled option. When enabled, this allows the removePairs job to also identify and remove pairs from your config.js that have been manually set to "enabled": false. This helps keep your configuration tidy and free of inactive, forgotten pairs.

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.

Keeping config.js Tidy

Over time, as you trade with Gunbot, you might manually disable pairs in your config.js for various reasons:

• A pair is underperforming, and you want to stop trading it temporarily.
• An exchange announces delisting or maintenance for a pair.
• You're testing a new strategy and disable pairs running older ones.

While these pairs are no longer actively trading, their configuration entries remain in config.js. If many such pairs accumulate, your configuration file can become lengthy and harder to manage. The pairs.removeDisabled option in a removePairs AutoConfig job provides an automated way to prune these inactive entries.

How pairs.removeDisabled: true Works

When you include pairs.removeDisabled: true in the pairs object of an AutoConfig job with type: "removePairs" (or "removePairs2"):

1. Primary Filter-Based Removal: The job first executes its standard logic. It evaluates all enabled pairs (that match pairs.include / pairs.exclude and are older than pairs.notRemoveBefore if set) against its main filters block. Enabled pairs passing these filters are removed (or have their BUY_ENABLED/SELL_ENABLED set to false, depending on Gunbot's specific removePairs implementation).

2. Disabled Pair Scan: Additionally and independently, if pairs.removeDisabled: true:

   • The job scans all pairs listed in config.js for the specified pairs.exchange.
   • It identifies any pair that has its top-level "enabled" parameter set to false.
   • These manually disabled pairs are then removed entirely from the config.js file.

Important Distinction: The main filters of the removePairs job (e.g., checking for low profit, low volume) are not applied to pairs being considered for removal by the removeDisabled: true logic. The only criterion for this specific cleanup action is "enabled": false.

Configuration Example

Here's how you would configure a removePairs job to also clean up disabled pairs:

{
  "configJanitorJob": {
    "enabled": true,
    "type": "removePairs",
    "schedule": "0 5 * * 1", // Runs weekly, early Monday morning
    "pairs": {
      "exchange": "kraken",
      "include": "-EUR,-USD", // Consider all EUR and USD pairs on Kraken
      "notRemoveBefore": 20160, // Only apply main filters to pairs older than 2 weeks (14 days)
      "removeDisabled": true, // User setting: Also remove any manually disabled pairs
      "noBag": false // For main filter removal, remove even if bag exists (example)
    },
    "filters": { // These filters apply to *enabled* pairs older than 'notRemoveBefore'
      "veryLowWeeklyTrades": {
        "filterType": "custom",
        "script": " return (this.pairVariables[this.exchangeName]?.[this.pairName]?.tradesThisWeek || 0) < 2;"
      }
    }
  }
}

In the configJanitorJob:

• It targets EUR and USD pairs on Kraken.
• Main Filter Logic: For enabled pairs older than 2 weeks, if they had fewer than 2 trades this week (checked by the custom filter), they would be removed by the primary action of the removePairs job.
• removeDisabled Logic: Because "removeDisabled": true, this job will also scan all Kraken pairs in config.js (regardless of the include or notRemoveBefore settings for this specific part of the logic). If it finds any pair like "USDT-BTC": { "enabled": false, ... } (assuming USDT-BTC was a Kraken pair in this context), it will remove the entire "USDT-BTC" entry from config.js. This happens irrespective of USDT-BTC's age, volume, or profitability.

Benefits of Using pairs.removeDisabled

1. Automated Configuration Hygiene: Keeps your config.js lean by automatically removing entries for pairs you've decided to stop trading.
2. Reduced Clutter: Makes your config.js easier to read, manage, and back up.
3. Prevents Accidental Reactivation: Ensures that pairs you've intentionally disabled don't get inadvertently re-enabled by other broad AutoConfig jobs if you're not careful with those jobs' include patterns.
4. Complements Dynamic Removal: Works alongside the filter-based removal of enabled pairs, providing a two-pronged approach to pair list management.

Important Considerations

• Irreversible Action: Removing a pair's configuration (whether it's an enabled pair via filters or a disabled pair via removeDisabled) is a permanent deletion from config.js for that run. If you want to trade that pair again, it will need to be re-added (manually or by an addPairs job). Always have backups of your config.js.
• Scope: removeDisabled: true applies to any pair on the job's target pairs.exchange that has "enabled": false. It's not restricted by the pairs.include or pairs.notRemoveBefore settings when performing this specific cleanup.
• Intention: Use this option when you are sure that disabled pairs are genuinely ones you no longer wish to keep configured, even in an inactive state. If you disable pairs very temporarily for quick tests, you might not want this option active in a frequently run removePairs job.
• Interaction with addPairs: If you have an aggressive addPairs job, it might re-add a pair that was just removed by removeDisabled: true if that pair still meets the addPairs criteria. Your overall AutoConfig logic should be cohesive.

The pairs.removeDisabled: true option is a helpful utility for maintaining a clean and current config.js file by automating the removal of pairs you've already decided to deactivate. It acts as a janitorial function within your removePairs AutoConfig jobs.