Stuck in a loop getting updates from telegram

```
2018-04-23T06:27:50.103470+00:00 app[web.1]: { Error: ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
2018-04-23T06:27:50.103485+00:00 app[web.1]: at tryCatcher (/app/node_modules/bluebird/js/release/util.js:16:23)
2018-04-23T06:27:50.103487+00:00 app[web.1]: at Promise._settlePromiseFromHandler (/app/node_modules/bluebird/js/release/promise.js:512:31)
2018-04-23T06:27:50.103488+00:00 app[web.1]: at Promise._settlePromise (/app/node_modules/bluebird/js/release/promise.js:569:18)
2018-04-23T06:27:50.103490+00:00 app[web.1]: at Promise._settlePromise0 (/app/node_modules/bluebird/js/release/promise.js:614:10)
2018-04-23T06:27:50.103492+00:00 app[web.1]: at Promise._settlePromises (/app/node_modules/bluebird/js/release/promise.js:693:18)
2018-04-23T06:27:50.103493+00:00 app[web.1]: at Async._drainQueue (/app/node_modules/bluebird/js/release/async.js:133:16)
2018-04-23T06:27:50.103495+00:00 app[web.1]: at Async._drainQueues (/app/node_modules/bluebird/js/release/async.js:143:10)
2018-04-23T06:27:50.103496+00:00 app[web.1]: at Immediate.Async.drainQueues (/app/node_modules/bluebird/js/release/async.js:17:14)
2018-04-23T06:27:50.103508+00:00 app[web.1]: at runCallback (timers.js:794:20)
2018-04-23T06:27:50.103510+00:00 app[web.1]: at tryOnImmediate (timers.js:752:5)
2018-04-23T06:27:50.103512+00:00 app[web.1]: at processImmediate [as _immediateCallback] (timers.js:729:5)
2018-04-23T06:27:50.103514+00:00 app[web.1]: code: 'ETELEGRAM',
```

Switching to webhook instead of polling will solve that one IMO.

The issue provides a Telegram polling error showing repeated 409 conflicts and suggests switching to webhooks. Start by locating the bot's update-retrieval setup and tracing how polling is started. Done means the conflict loop is prevented and the bot continues receiving updates through the selected approach.

Written by the indexing model from the issue text.