How to pass signals between Dhan Cloud strategies without manual intervention

APIs, Automation, Algos & Code
1

Subject: Architecture question — passing signals between strategies + exit monitor pattern

Hi,

Building a multi-strategy setup on Dhan Cloud and hit a specific architecture gap. Have already validated the individual pieces — looking for the right pattern to connect them.

What’s working:

  • Scanner strategy: historical_daily_data for a large universe of symbols, pure Python indicator computation, prints signal list to console :white_check_mark:

  • Executor strategy: reads signal string from {{SIGNALS}} ENV variable, calls place_order() :white_check_mark:

  • Stop-loss order: direct urllib POST to https://api.dhan.co/v2/forever/orders :white_check_mark:

The gap — signal passing between scanner and executor:

When adding Supabase urllib read inside the executor alongside place_order(), the security scanner flags it HIGH. So the intended flow — scanner POSTs signals to Supabase at 3:35 PM → executor GETs signals from Supabase next morning → places orders — is blocked at the executor end.

Current workaround is manual: copy signal string from scanner console, paste into executor Variables Tab each evening. Works but defeats the purpose of scheduling.

Question 1 (most important): Can a running strategy programmatically write or update a Global Variable?

If the scanner can update a Global Variable (e.g. SIGNALS) at runtime, the executor can read it via {{SIGNALS}} automatically — no external service needed. Is there an API or SDK method for this, or any other native way for one strategy to pass data to another?

Question 2: What external domains are allowed in a strategy that also calls place_order()?

urllib calls to https://api.dhan.co/* pass the security scanner fine. Is there a whitelist of allowed external domains? Can urllib to a third-party service coexist with place_order(), or is any non-Dhan external call combined with a financial action always flagged HIGH?

Question 3: Exit monitor architecture

Want a separate strategy to handle exits: call get_holdings(), fetch recent candle history via historical_daily_data(), compute an exit indicator, and call place_order() (SELL) on condition. Does this combination pass the security scanner? Or does get_holdings + place_order in the same script trigger the same HIGH flag?

Question 4: Any built-in cross-strategy data sharing?

Is there any native Dhan Cloud mechanism to share data between strategies beyond Global Variables? For example, can one strategy trigger or pass parameters to another at runtime?

Thanks in advance — any documentation or working templates for the scanner→executor handoff pattern would be very helpful.