Format and current limitations

Understand saved rule rows, dependencies and current execution limits.

Fields

Field	Type	Meaning
enabled	Boolean	Whether Smart Scan evaluates this rule.
name	String	Rule name; referenced in the UI and saved filename.
comments	String	Explanation for the operator.
match	Array of strings	Passive trigger rows.
execute	Array of strings	Active action rows.
scope	Integer	Legacy serialized field; the current action scope is in each execute row.
match_enabled, exec_enabled	Booleans	Legacy/editor properties; row flags control the serialized conditions/actions.
operator, profile_type, passive_profile_type, type, active_profile_type	Strings	Legacy/editor properties preserved in exports; do not replace the row arrays.

Match row

enabled,operator,profile type,profile name
true,,Passive Request,Example_Debug_Query_Parameter

Operators offered by the editor are And and Or, with an empty first row. Types are Passive Request and Passive Response. Profile name is an exact reference to an installed profile; the evaluator resolves its reported issue name.

Execute row

enabled,type,name,scope
true,Profile,Example_Marker_Reflection,All Matches
true,Tag,Examples,All Matches

Type is Profile or Tag. Scope labels are All Matches and First Match. Only enabled active profiles are eligible. Avoid overlapping actions unless repeated work is intended; tag membership is live profile metadata.

Current execution limitations

And is not a strict combined prerequisite

The editor stores groups, but the current evaluator processes an individual passive issue and checks whether its issue name appears in a configured group. It does not accumulate all request/response conditions and require every And member to match first.

Do not describe a request-profile And response-profile rule as guaranteed to require both. Prefer one sufficiently precise passive trigger for predictable rules, or manually verify the intended combined condition before launching active work. This documentation update does not change that engine behavior.

First Match is not a reliable traffic boundary

The current action tracking uses in-memory host/name matching and does not provide a strict once-per-scheme/host/port identity. Its matching loop can allow repeated actions. Do not rely on it for an exact one-run limit, cross-session deduplication or durable history.

For controlled use, submit a small explicit request set, choose narrow actions and apply active budgets. Pro's per-host profile planning is a separate feature; it does not repair the rule evaluator's semantics.

Profile names and issue names

Rules store profile names, but triggers are resolved through their issue names. Duplicate issue names can make distinct passive detectors indistinguishable to the evaluator. Use distinct, descriptive names and test the rule with positive and negative fixtures.

Dependency and location

Missing/disabled action profiles cannot execute. Rule files do not embed the referenced profiles. Neither .bbre nor Server's profile catalogue is the current rule storage location: use .bb files in Pro's rules directory.