# Changelog of Telegram Channel Analytics — Subscribers, Reach & Stats (`lergassy/telegram-channel-analytics`) Actor

- **URL**: https://apify.com/lergassy/telegram-channel-analytics/changelog.md
- **Full Actor documentation**: https://apify.com/lergassy/telegram-channel-analytics.md

## Changelog

### 2026-10-02

- With a maximum cost per run set, post rows are now counted at the post price, so capped runs deliver as many rows as your limit covers; held-back posts are never charged.
- Runs that delivered everything you asked for are no longer labelled as stopped at the maximum cost.
- Default memory now scales with posts per channel and concurrency, so small runs use less memory.

### 2026-10-01

- Runs capped by your maximum cost per run no longer stop early before the limit is actually reached.

### 2026-09-29

- The channel list is now marked as a required input, so an empty form is caught before the run starts.

### 2026-09-27

- Runs stop cleanly at your maximum cost per run instead of being aborted; nothing beyond your limit is written or charged.

### 2026-09-24

- Reaction counts are read correctly again; previously posts with emoji reactions could report 0.

### 2026-09-21

- Runs with Apify Proxy switched on no longer fail with "fetch failed".

### 2026-09-04

- Initial release: turns any public Telegram channel into one row of analytics: subscribers, reach (median views per subscriber), posting frequency, best hours, content mix and top posts, with optional per-post rows; no API key, phone number or account needed.