Observe first. Choose deliberately.
Observe
Save matching evidence without changing group membership. The default action.
Block
Ban a rule-matched member so they cannot rejoin while the ban remains.
Remove
Ban, then unban to allow rejoining. The member is not automatically added back.
Message deletion and required permissions
History is affected. Telegram’s ban operation deletes the member’s message history in supergroups. Both Block and Remove use it. Remove cannot promise to preserve history.
Automatic actions require enabled group rules and an explicitly selected Block or Remove action. The bot needs permission to delete messages and restrict members. TGDog first attempts to delete currently matched cached messages, in batches of up to 100, before member handling. Explicit deletion is generally limited to messages younger than 48 hours. Saving rules can examine already cached messages and queue actions, not only future messages.
Inspect results and recover incomplete actions
Inspect Execution records for pending, retry, successful, failed, skipped, or unknown outcomes. An unknown network response is not proof of success. An incomplete Remove may need unban recovery; resolve it before disconnecting or clearing local data.
The current implementation has mock-tested action handling. Real-group action verification is not established in the source project documentation. Validate the behavior in a designated test group before relying on it in production.
Source: Telegram member ban semantics
Check your setup
- Observe saves evidence without member handling.
- Block and Remove affect message history.
- An unknown response must be checked, not treated as success.
Where to go next
If you are setting up TGDog for the first time, follow the complete How to use tutorial. For a deeper explanation of another topic, return to the Guide library.