Gallery Bulk Actions and Maintenance

Summary

Bulk actions are powerful and risky. This guide explains safe batch operations and maintenance cadence. 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

• Clean large media sets efficiently.
• Reduce accidental destructive actions.
• Maintain script asset integrity.

Before you start

• Confirm selection count and identities.
• Verify category target exists.
• Ensure assets are not currently critical for live scripts.

Step-by-step workflow

1. Select assets in grid.
2. Choose bulk action (delete or category update).
3. Double-check selected asset list.
4. Apply action and wait for success toast.
5. Refresh and verify expected final state.
6. Update script mappings if assets moved or removed.

Key states and error handling

• Bulk action guard: 'Select at least one category' for category-required operations.
• Delete success toast: 'Selected media deleted'.
• Bulk delete failure fallback: 'Bulk delete failed'.

Best practices

• Perform destructive operations during low-traffic windows.
• Export/backup critical asset ids before bulk delete.
• Use category moves before delete when uncertain.

Troubleshooting

• If wrong assets selected, cancel and rebuild selection carefully.
• If operation fails, split into smaller batches.
• If scripts break after cleanup, remap missing media in script steps.
• If issue persists after one clean retry, capture exact toast/banner text, selected bot, and timestamp before escalation.

UI reference (what each control does)

• Search and type filters control retrieval speed in large media libraries.
• Category selection changes query scope and can hide valid assets if misconfigured.
• Direct upload size limits differ by media type and must be respected.
• Audio pipeline only supports .ogg/.mp3 with strict size constraints.
• Telegram upload sessions are used for controlled constrained ingest paths.
• Batch limits exist for Telegram session uploads and require chunking.
• Bulk actions are powerful and must be validated before applying.
• Upload toasts classify most operational upload failures quickly.

Operator checklist (before shipping changes)

• Verify file formats and size before upload.
• Select correct bot for Telegram upload sessions.
• Upload in small controlled batches to reduce retries.
• Apply categories immediately after successful upload.
• Run periodic uncategorized cleanup to keep retrieval fast.
• Revalidate script media mappings after bulk maintenance.

Real-world scenario

A campaign upload fails minutes before launch. The operator splits files into compliant batches, converts invalid audio formats, runs a Telegram upload session for constrained files, and confirms all assets are visible before script activation.

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.