Scheduling, Delays & Edit Limits

Overview

High-volume instant forwarding can trigger Telegram anti-spam detection or overload downstream subscribers. AutoTelegramForward provides comprehensive timing controls: jittered delays, operating schedules, and edit-synchronization cutoffs.

Max Time Edit Threshold (max_time_edit)

In high-frequency news channels, authors often edit older posts (e.g., correcting typos hours or days later). Attempting to synchronize edits on weeks-old posts wastes Telegram API quotas and creates unnecessary traffic.

Anti-Detection Forwarding Delays (Jitter)

To mimic authentic human curation and avoid algorithmic rate-limit penalties, each rule can be configured with randomized forwarding delays:

• Min Delay: Minimum wait time (e.g., 5 seconds) before dispatching to destination.
• Max Delay: Maximum wait time (e.g., 25 seconds).
• Jitter Distribution: The durable queue calculates a uniform random delay between min and max bounds for every message.

Daily Operating Windows

Ensure posts are only forwarded during appropriate daytime hours for your audience's timezone:

# Example schedule configuration
schedule:
  enabled: true
  timezone: "UTC"
  active_hours: "08:00-22:00"
  queue_outside_hours: true  # Store in durable queue until 08:00

Edit Re-Filtering Engine

When an existing post is edited in the source channel, AutoTelegramForward doesn't just re-send the edit blindly—it executes the full FilterEngine and Cleaner again. If a newly edited post now contains blacklisted terms or prohibited links, the forwarded message in the destination channel can be automatically deleted or updated based on rule policy.