Gallery Upload Errors and Recovery

Summary

Use this focused playbook when uploads fail repeatedly and you need immediate recovery without guesswork. 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

• Shorten upload incident resolution time.
• Prevent repeated invalid attempts.
• Keep media pipeline stable during launches.

Before you start

• Capture exact error text.
• Identify direct upload vs Telegram session path.
• Check bot connectivity for Telegram path.

Step-by-step workflow

1. Classify error category (selection, format, size, session, mutation).
2. Apply the matching fix once.
3. Retry upload with minimal batch.
4. Validate success toast and grid visibility.
5. Continue remaining files gradually.
6. Log pattern if error recurs.

Key states and error handling

• Known messages provide direct root-cause hints.
• Generic upload fallback indicates mutation-level failure.
• Repeated failures usually combine format and session issues.

Best practices

• Never retry blindly; fix root cause first.
• Use one-file smoke test after fixing format/size.
• Escalate only with concrete error message and file metadata.

Troubleshooting

• Format error: convert file and retry.
• Size error: compress/split and retry.
• Session error: recreate session with explicit bot selection.
• 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.