1 minute readFixedAgent-ready
Routing uses your configured policy strategy
Stored routing strategies and their constraints affect requests without an explicit routing choice.
Review existing policies because their configured strategy and limits can change which function receives traffic.
- An explicit function selection or request routing preference takes precedence where supported.
- The policy's rules, strategy and fallbacks determine its remaining choices.
- Weighted strategies need usable weights; rule-based policies need rules. Invalid configurations are rejected when saved.
Check cost and latency ceilings alongside available functions. Use request traces to confirm the policy selects the function you expect.