<b>SOP: Smartlink change rollback</b>
Purpose: undo a bad routing edit in under two minutes instead of debugging live traffic.
☐ Step 1 — Before any edit, export the current rule set and weights to a dated file.
☐ Step 2 — Make one change at a time. Bundled edits make rollback guesswork.
☐ Step 3 — Watch EPC and fallback-rate for 30 minutes post-change. A fallback spike means a rule broke.
☐ Step 4 — If EPC drops more than 20% or fallback exceeds 10%, restore the exported set immediately.
☐ Step 5 — Only then diagnose what the change broke, on a copy, not on live traffic.
☐ Step 6 — Log every change with timestamp so you can correlate metric shifts to edits.
Keep the last five exports. The break you didn't notice today shows up in tomorrow's numbers.
Smartlink Ops
@SmartlinkOps
<b>SOP: Smartlink change rollback</b>
Этот пост опубликован в Telegram-канале Smartlink Ops. Подписаться можно по ссылке: @SmartlinkOps.