Guardian rule ignores stored-value `offset_ticks` and exits at 1 tick instead of configured target

Advanced automation available in Guardian - Chat with others and share files here.
Post Reply
donnamgifts
Posts: 1
Joined: Sun Apr 19, 2026 5:57 pm

Hi all,

I am trying to run a Bet Angel Guardian automation where:

- Python selects the runner and arms the trade
- Python writes stored values for the nominated selection
- Guardian is the only component that places and manages the live bets
- Guardian should handle both the entry and the offset/green exit

I am looking for help with one specific issue:

- the exit appears to be behaving like a 1-tick offset even when I am trying to send a larger stored-value offset such as 2 ticks

**Current setup**

I have two Guardian rules:

1. `Lay Scalp + Disarm Lay`
2. `Back Scalp + Disarm Back`

Both rules are configured like this on the Parameters tab:

- `Place at`: `Stored Value price`
- name: `entry_price`
- `Stake`: `Stored Value Stake`
- name: `stake`
- action: `Offset bet with greening and Stop`
- `Override settings with StoredValues`: enabled
- offset SV name: `offset_ticks`
- stop SV name: `stop_ticks`
- FOK SV name: `fok_delay`
- scope: `the Current Selection`

The Stored Values tab inside the rule editor is empty because Python is writing the values externally.

**What Python is writing**

Python writes these stored values for the runner:

- `entry_price`
- `stake`
- `offset_ticks`
- `stop_ticks`
- `fok_delay`

The logs show values like:

```text
[guardian] Armed: ... off=2 stop=1 fok=10.0s ...

any help appreciated as i am losing the will to live :shock:
Post Reply

Return to “Bet Angel - Automation”