🙂 NLP-разработчик в команду качества претрейна Alice LLM Ищем ML-разработчика, который будет улучшать качество претрейна Alice AI LLM. Это направление, отвечающее за умность базовой модели и качество данных. Какие задачи вас ждут: • Эксперименты с претрейн-моделями Ставить и анализировать вычислительно тяжёлые эксперименты с претрейн-стадией. Проверять гипотезы об источниках прироста ризонинг-способностей внутри р…

Channel
Яндекс нанимает | Вакансии для разработчиков
@ya_jobs
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry
32,803subscribers
+361 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001165814759 |
|---|---|
| Type | Channel |
| Username | @ya_jobs |
| Description | Актуальные вакансии для разработчиков в Яндекс Папка с каналами Яндекса для разработчиков: https://t.me/addlist/Hrq31w2p1vUyOGZi Все вакансии для разработчиков: https://ya.cc/t/t9Tlu_e74DqkMQ Номер заявления в РКН: 4962644000 |
| Created | 17 August 2020 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/ya_jobs |
Topic
Job listings — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 04:41 | 32,803 | +47 |
| 19 Sept 2026, 00:19 | 32,756 | +31 |
| 16 Sept 2026, 12:40 | 32,725 | +7 |
| 13 Sept 2026, 04:42 | 32,718 | +10 |
| 11 Sept 2026, 04:16 | 32,708 | +15 |
| 8 Sept 2026, 07:54 | 32,693 | +29 |
| 5 Sept 2026, 01:38 | 32,664 | +27 |
| 3 Sept 2026, 09:33 | 32,637 | +14 |
| 2 Sept 2026, 02:45 | 32,623 | +21 |
| 31 Aug 2026, 23:28 | 32,602 | -1 |
| 31 Aug 2026, 01:07 | 32,603 | -1 |
| 30 Aug 2026, 02:16 | 32,604 | +7 |
| 28 Aug 2026, 23:47 | 32,597 | -6 |
| 28 Aug 2026, 01:03 | 32,603 | +12 |
| 27 Aug 2026, 00:35 | 32,591 | +7 |
| 26 Aug 2026, 03:02 | 32,584 | +6 |
| 25 Aug 2026, 06:27 | 32,578 | +8 |
| 24 Aug 2026, 05:55 | 32,570 | +4 |
| 22 Aug 2026, 17:08 | 32,566 | +18 |
| 21 Aug 2026, 07:18 | 32,548 | first reading |
Engagement
152 posts held, back to 29 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 82 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 5.70%
- avg views ÷ 32,803 subscribers
- Avg views / post
- 1,870
- 77 posts measured
- Reaction rate
- 0.106%
- reactions ÷ views · ER floor
- Posts in window
- 77
- of 152 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 50 of 77 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 25 September 2026 |
|---|---|
| Posts held | 152 (29 July 2026 – 25 September 2026) |
| Views total | 143,903 |
| Reactions total | 101 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 26 Sept 2026, 07:06 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Photos
- ≈704
- Videos
- ≈103
- Links
- ≈5,620
Lifetime counters from Telegram’s own channel header, read 26 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
214 reactions across 76 posts, in 10 distinct kinds. The most used accounts for 47.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 102 | 47.7% | |
| 👍 | 38 | 17.8% | |
| 🔥 | 38 | 17.8% | |
| 😁 | 14 | 6.54% | |
| 👎 | 8 | 3.74% | |
| 🤩 | 5 | 2.34% | |
| 🤔 | 4 | 1.87% | |
| 🤬 | 2 | 0.935% | |
| 🤯 | 2 | 0.935% | |
| 😱 | 1 | 0.467% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 97 of the 152 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 216 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 152 most recent posts we hold, published 29 July 2026 to 25 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Advertising
- Ad load
- 0.658%
- 1 of 152 posts carry an ad marker
- Regulatory tokens
- 1
- posts carrying an erid · 1 distinct token
- Median views · ads
- 1,790
- over 1 measured post
- Median views · rest
- 2,040
- over 151 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| CQH36pWzJqE1dR7FuZ8VXKQnZsv3AXmjHd4tnmJikBC6yK | 1 | 14 September 2026 | 14 September 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 152 most recent posts we hold, published 29 July 2026 to 25 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Recent posts
🍔 Аналитик промоэффективности в Яндекс Еду Привет! Мы работаем над тем, чтобы пользователи Яндекс Еды были довольны и оставались с нами: используем промоакции и меняем продукт, чтобы развивать бизнес. Сейчас мы ищем аналитика промоэффективности. Эта роль подойдёт тому, кому интересно совершенствовать клиентские механики и ставить эксперименты. Антон Рябченко, руководитель службы аналитики роста Промо — один из ключ…
❤️ SRE в Поиск Поиском Яндекса пользуются сотни миллионов пользователей, сотни тысяч ядер обрабатывают миллиарды запросов в сутки, а некоторые микросервисы держат десятки миллионов RPS, обрабатывая петабайты горячих данных. Такой масштаб и критичность накладывает серьёзные требования на надёжность. Наша команда работает над всей инфраструктурой основного веб-поиска и поиска по картинкам. Мы ищем SRE, способных внедр…
🔥3
📕 Станьте экспертом на курсе Яндекс Практикума В Яндекс Практикуме мы обучаем цифровым профессиям в лучших традициях Яндекса: с технологиями и поддержкой экспертов. В обучении студентов сопровождают наставники. 📌 Что делает наставник? Помогает студентам на протяжении обучения: отвечает на вопросы, проводит воркшопы и Q&A-сессии, направляет и поддерживает. Сейчас ищем действующих разработчиков на роль наставника ср…
❤1👎1
📦 Разработчик на Java в команду контентной платформы Маркета Привет! Мы развиваем сервисы, от которых зависит, как устроен каталог и как товары отображаются на витрине. В нашей зоне ответственности — десятки тысяч категорий и параметров, более 2 млрд карточек и около 2 тыс. изменений групп карточек каждую секунду. Алексей Тришин, руководитель службы разработки контентной платформы Сейчас мы строим микросервисную ар…
😁1
❣️ ML-разработчик в Международный Поиск Если какая-то технология приносит деньги, то она быстро становится сложносочинённой. Реклама в Яндексе как раз такая — одна из самых технологически сложных систем. Мы работаем на международном рынке рекламы, у нас весь рекламный стек свой. В команде можно и нужно крутить все части современной рекламной системы: кандидатогенерацию, предсказатели, рекомендации. Мы хотим улучшит…
🖤 Аналитик-разработчик в команду разметки и анализа данных Фантеха Привет! Меня зовут Лёша Царёв, и я руковожу командой разметки и анализа данных в Фантехе Яндекса. Наша команда занимается самыми разными задачами в области дата-майнинга для контентных сервисов, а именно Яндекс Музыки, Кинопоиска, Яндекс Книг и т. д. Я ищу аналитика-разработчика, который поможет нам сделать рекомендации и поиск в наших сервисах лучше…
👍4
❤️ Аналитик (KPI-сессии) в команду аналитики поиска Наша команда отвечает за прогнозирование и анализ ключевых KPI поискового продукта. Ищем аналитика, которому интересно работать на стыке продукта, бизнеса и данных. Важно понимать, что стоит за изменениями метрик, задавать правильные вопросы и объяснять результаты понятным языком. Какие задачи вас ждут: • Анализировать отклонения от прогноза Вы будете декомпозиро…
❤1👍1
🤍 Руководитель группы разработки Arcanum в DevTools Привет, я Тимур, руководитель службы инструментов репозитория. Мы создаём инструменты, которыми инженеры Яндекса пользуются для разработки. Вы поможете нам вывести надёжность и удобство нашей платформы на новый уровень. Если вам близка миссия улучшать жизнь разработчиков — вам точно к нам. Тимур Торубаров, руководитель службы инструментов репозитория Наша команда …
❤1👎1
🙂Инженер данных в отдел аналитики Alice AI Наша команда разрабатывает базовую технологию, которая лежит в основе Алисы, Нейропоиска, Нейробраузера и многих других продуктов — большую языковую модель Alice AI. Мы также учим модель работать с агентами. Ещё мы создаём инфраструктуру бенчмарков, чтобы измерять, насколько новая версия модели лучше предыдущих версий и продуктов конкурентов. Какие задачи вас ждут • Разви…
🚕 Руководитель группы моделирования симуляционной сцены в Автономный транспорт Чтобы эффективно оценивать качество релизов ПО беспилотного автомобиля, в Яндексе разработали систему симуляции. Она позволяет проанализировать поведение авто в виртуальном окружении, оценить влияние внешних и внутренних факторов на поведение автономного транспорта и предсказать последствия выбранного поведения. Какие задачи вас ждут • …
🖤 ML-разработчик в Рекламу Мы умеем на лету генерировать персонализированные тексты рекламных объявлений, адаптируя предложение рекламодателя для пользователей. Внедряем генеративные, дискриминативные и ранжирующие модели в одну из крупнейших рекомендательных платформ. Вы станете работать в команде с сильными исследователями и инженерами, перенимать их опыт и влиять на то, как будет выглядеть реклама в интернете зав…
Showing the 12 most recent of 152 posts we hold for @ya_jobs. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
@Yandex4Developers · 28,5057 postsYandex for Backend
@yandexforbackend · 10,1223 postsYandex for Security
@yandexforsecurity · 3,3443 postsYandex for Analytics
@yandexforanalytics · 9,4472 postsPractical ML Conf
@Practical_ML_Conf · 8431 post+1 в команду Яндекс Практикума
@practicum_experts · 24,1351 postТЕХНО: Яндекс про технологии
@techno_yandex · 226,2411 postYandex for ML
@yandexforml · 18,8541 post
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@Yandex4Developers · 28,505#1
@Young_and_Yandex · 111,329#2
@yandexforbackend · 10,122#3
@yandex · 582,624#4
@vkjobs · 25,707#5
@Education_Yandex · 37,959#6
@avitotech · 25,625#7
@ozon_tech · 29,768#8
@vacancy_cs · 16,939#9
@yandexforml · 18,854#10
@t_crew · 43,385#11
@techno_yandex · 226,241#12
@cryptovalerii · 30,829#13
@postypashki_old · 45,531#14
@dev_connectablejobs · 27,959#15
@avito_career · 66,216#16
@kod_zheltyi · 33,061#17
@rozetked · 656,361#18
@d_code · 406,147#19
@latech · 10,983#20
@habr_com · 132,465#21
@yandexhabr · 3,375#22
@airi_research_institute · 13,654#23
@yandex4frontend · 10,858#24
@algoses · 12,070#25
@IT_picnic · 23,126#26
@ya_jobs_pm · 29,939#27
@yandex_infrastructure · 4,682#28
@fcs_hse · 14,370#29
@deep_school · 10,738#30
@not_boring_ds · 12,052#31
@ozon_tech_vacancies · 3,594#32
@ai_machinelearning_big_data · 279,417#33
@data_secrets · 94,138#34
@mintsifry · 234,926#35
@careersber · 136,237#36
@yandexmuseum · 9,080#37
@datasciencejobs · 22,137#38
@yandexcloudnews · 21,888#39
@zloy_kollega · 45,024#40
@g_jobchannel · 18,874#41
@MLunderhood · 4,805#42
@tproger · 78,305#43
@vcnews · 112,033#44
@zarubezhom_jobs · 103,632#45
@start_ds · 11,495#46
@tech_priestess · 14,890#47
@mtsbankcareer · 30,329#48
@tired_glebmikheev · 17,248#49
@habr_career · 33,171#50
@ecomtech_channel · 7,580#51
@codecamp · 181,400#52
@cloud_track · 8,057#53
@goproglib · 24,076#54
@alfadigital_jobs · 54,435#55
@ithumor · 60,568#56
@thecodemedia · 49,237#57
@chad_protocol · 11,571#58
@datafeeling · 14,242#59
@datajobschannel · 12,272#60
@zarplatnik_analytics · 11,546#61
@evacuatejobs · 135,997#62
@tagir_analyzes · 11,702#63
@journal_yandex_education · 13,420#64
@practicumtech · 11,237#65
@tbank_education · 113,416#66
@bbbreaking · 1,974,402#67
@odsjobs · 14,059#68
@meduzalive · 1,122,482#69
@ai_newz · 96,889#70
@lovedeathtransformers · 25,677#71
@ebaresearch · 5,333#72
@seeallochnaya · 79,594#73
@addmeto · 71,835#74
@exploitex · 2,041,128#75
@hrlunapark · 20,296#76
@TeamAvito · 16,332#77
@zheltyi_ai · 9,387#78
@tb_invest_official · 528,596#79
@tbank · 331,521#80
@denissexy · 137,325#81
@not_boring_ds_jobs · 9,120#82
@phystechcareerchannel · 7,254#83
@kantor_ai · 12,217#84
@kinopoisk · 806,604#85
@new_yorko_times · 10,554#86
@foranalysts · 36,643#87
@godevjob · 11,278#88
@datajob · 14,805#89
@media_rare · 25,869#90
@book_cube · 15,749#91
@ftsec · 19,382#92
@rybolos_channel · 19,011#93
@Golang_google · 40,461#94
@computerscienceabroad · 4,945#95
@NeuralShit · 53,680#96
Read from Telegram’s recommendation API, most recently 5 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@Yandex4Developers · 28,505
Telegram ranks this channel #3 of 94 here — alongside 93 others — read 9 September 2026
@vkjobs · 25,707
Telegram ranks this channel #8 of 97 here — alongside 96 others — read 13 September 2026
@habr_career · 33,171
Telegram ranks this channel #8 of 97 here — alongside 96 others — read 4 September 2026
@Young_and_Yandex · 111,329
Telegram ranks this channel #10 of 92 here — alongside 91 others — read 14 August 2026
@Education_Yandex · 37,959
Telegram ranks this channel #12 of 96 here — alongside 95 others — read 31 August 2026
@t_crew · 43,385
Telegram ranks this channel #12 of 95 here — alongside 94 others — read 29 August 2026
@thecodemedia · 49,237
Telegram ranks this channel #14 of 97 here — alongside 96 others — read 25 August 2026
@postypashki_old · 45,531
Telegram ranks this channel #17 of 90 here — alongside 89 others — read 28 August 2026
@zloy_kollega · 45,024
Telegram ranks this channel #18 of 98 here — alongside 97 others — read 28 August 2026
@ya_jobs_pm · 29,939
Telegram ranks this channel #20 of 98 here — alongside 97 others — read 8 September 2026
@avitotech · 25,625
Telegram ranks this channel #21 of 96 here — alongside 95 others — read 14 September 2026
@ozon_tech · 29,768
Telegram ranks this channel #22 of 98 here — alongside 97 others — read 8 September 2026
@avito_career · 66,216
Telegram ranks this channel #22 of 98 here — alongside 97 others — read 21 August 2026
@kod_zheltyi · 33,061
Telegram ranks this channel #23 of 96 here — alongside 95 others — read 4 September 2026
@yandex · 582,624
Telegram ranks this channel #23 of 96 here — alongside 95 others — read 9 August 2026
@techno_yandex · 226,241
Telegram ranks this channel #24 of 96 here — alongside 95 others — read 11 August 2026
@careersber · 136,237
Telegram ranks this channel #25 of 96 here — alongside 95 others — read 13 August 2026
@yandexcloudnews · 21,888
Telegram ranks this channel #32 of 97 here — alongside 96 others — read 22 September 2026
@yndx_practicum · 34,046
Telegram ranks this channel #36 of 97 here — alongside 96 others — read 3 September 2026
@ozonteam · 22,918
Telegram ranks this channel #42 of 89 here — alongside 88 others — read 19 September 2026
@datasciencejobs · 22,137
Telegram ranks this channel #44 of 93 here — alongside 92 others — read 21 September 2026
@mtsbankcareer · 30,329
Telegram ranks this channel #56 of 99 here — alongside 98 others — read 7 September 2026
@Igromir_cloud · 58,836
Telegram ranks this channel #58 of 89 here — alongside 88 others — read 22 August 2026
@tbank_education · 113,416
Telegram ranks this channel #59 of 91 here — alongside 90 others — read 14 August 2026
This channel appears in 25 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 25 September 2026 — this entry's latest reading, not the date you are reading this.
“Яндекс нанимает | Вакансии для разработчиков” (@ya_jobs), 32,803 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/ya_jobs.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.