Scripts Edit, Reorder, and Delete Operations

Summary

Long-running workspaces need script maintenance discipline. This article covers operations that prevent clutter and execution mistakes. For operators, this page should be used as a decision surface, not only as a UI form. Always pair page actions with downstream validation in the relevant live workflow.

What this page is for

• Keep script library maintainable.
• Avoid priority conflicts after updates.
• Retire obsolete scripts safely.

Before you start

• Identify script ownership before edits.
• Check if script is currently active.
• Plan replacement path before deletion.

Step-by-step workflow

1. Open script list for selected mode.
2. Edit only one script batch at a time.
3. Reorder priorities and verify neighboring scripts.
4. Deactivate script before major rewrite.
5. Delete only after replacement is ready.
6. Retest final ordering in live threads.

Key states and error handling

• Update fallback: 'Failed to update the script.'
• Delete action removes script from active workflow map.
• Priority swaps can affect adjacent scripts immediately.

Best practices

• Archive logic in internal notes before delete.
• Prefer deactivation before permanent removal.
• Re-run sanity tests after each reorder.

Troubleshooting

• If reorder results look wrong, refresh and re-evaluate final indices.
• If delete removes wrong item, confirm selected script id before action.
• If updates fail repeatedly, split changes into smaller operations.
• If issue persists after one clean retry, capture exact toast/banner text, selected bot, and timestamp before escalation.

UI reference (what each control does)

• Scripts are scoped by selected bot and selected mode (paid media or sell link).
• Script active state controls whether it can drive live offer behavior.
• Priority ordering changes execution order and can alter conversion outcomes immediately.
• Step type (free vs paid) determines monetization behavior in the flow.
• Paid steps rely on stars price and optional minimum boundaries.
• ai_step_context influences generated transition quality and negotiation framing.
• media_asset_id mapping is required for robust paid-media delivery paths.
• Mutation toasts are primary indicators for create/update/delete failures.

Operator checklist (before shipping changes)

• Confirm bot and mode before creating or editing scripts.
• Build complete steps before activating new scripts in production.
• Test one changed script at a time in live conversations.
• Use conservative pricing increments and track each revision.
• Re-check priority after adding or deleting scripts.
• Keep fallback script ready before major rewrites.

Real-world scenario

A new paid script underperforms after launch. The operator verifies mode selection, checks step mapping and media ids, rolls back the latest pricing jump, and restores stable conversion before retesting incremental changes.

1. Identify the exact scope (bot, period, module) before any change.
2. Apply one targeted correction based on observed UI state and messages.
3. Validate outcome in the live operational flow linked to this page.
4. Document the final state so future incidents can be solved faster.