Skip to content
This repository has been archived by the owner on Jun 8, 2023. It is now read-only.

NotificationChannels\Telegram\Exceptions\CouldNotSendNotification: Telegram responded with an error 400 - Bad Request: chat not found #391

Closed
sentry-io bot opened this issue Jan 11, 2023 · 0 comments · Fixed by #392
Assignees

Comments

@sentry-io
Copy link

sentry-io bot commented Jan 11, 2023

Sentry Issue: STAGING-APP-6

GuzzleHttp\Exception\ClientException: Client error: `POST https://api.telegram.org/bot393828013:AAEae8whNPAHi2EIyRmssVY51XQqsV7o_3M/sendMessage` resulted in a `400 Bad Request` response:
{"ok":false,"error_code":400,"description":"Bad Request: chat not found"}

  File "/app/Domains/Contact/ManageReminders/Jobs/ProcessScheduledContactReminders.php", line 50, in App\Domains\Contact\ManageReminders\Jobs\ProcessScheduledContactReminders::handle
    ->notify(new ReminderTriggered($channel, $contactReminder->label, $contactName));
  File "/artisan", line 37
    new Symfony\Component\Console\Output\ConsoleOutput
...
(53 additional frame(s) were not displayed)

NotificationChannels\Telegram\Exceptions\CouldNotSendNotification: Telegram responded with an error `400 - Bad Request: chat not found`
  File "/app/Domains/Contact/ManageReminders/Jobs/ProcessScheduledContactReminders.php", line 50, in App\Domains\Contact\ManageReminders\Jobs\ProcessScheduledContactReminders::handle
    ->notify(new ReminderTriggered($channel, $contactReminder->label, $contactName));
  File "/artisan", line 37
    new Symfony\Component\Console\Output\ConsoleOutput
...
(42 additional frame(s) were not displayed)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant