client.monitor.alerts.list does not fetch 30003, 30005 errors although they are seen on twilio monitor GUI

Open
#728 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
api

Research direction

Start by reproducing the client.monitor.alerts.list(start_date: 1.week.ago) query and filtering for error codes 30003 and 30005, using the reported Ruby and twilio-ruby versions. Compare the returned alerts with the corresponding Twilio Monitor GUI and Message logs; done means the discrepancy is explained or consistently reproduced.

Written by the indexing model from the issue text.

Description

priority: medium status: waiting for feedback type: bug
Issue Summary

We have code that fetches all twilio alerts within the last 1 week. For each of these alerts, we create an alert object (TwilioAlert) in our DB. However, we have not created TwilioAlert with error_code 30003, 30005 before (we've been using this code for years). But we suddenly started seeing these errors come in starting July 1st (no code change to the code shown below). And now we've suddenly stopped seeing them since July 15th, but they are present in twilio monitor GUI. Furthermore, according to twilio monitor GUI, we have had these alerts at least for the last 4 months, we just haven't been seeing them be created in our db. Has anyone else had this issue and what could explain this discrepancy?

Currently, I see many 30003 errors on July 23rd, 2024 when I search for them in Message logs on Twilio but if I search for the error_code 30003 using:
client.monitor.alerts.list(start_date: 1.week.ago).filter { |a| a.error_code == '30003' }, I don't see any come back.

I have reached out to twilio support and received no indication that they have changed anything. I'm wondering if anyone is experiencing similar issues or has any suggestions for why this might be happening.

Code Snippet
      client = Twilio::REST::Client.new

      alerts = client.monitor.alerts.list(start_date: 1.week.ago)

      alerts.each do |alert|
        TwilioAlert.find_or_create_by(resource_sid: alert.resource_sid) do |record|
          record.error_code = alert.error_code
          record.request_url = alert.request_url
          record.request_variables = alert.request_variables
          record.date_alert_created = alert.date_created
          record.resolve_status = :unresolved
        end
      end
Technical details:
  • twilio-ruby version: 7.2.1 (Jun 28 -> Jul 10), 7.2.3 (since Jul 10)
  • ruby version: 3.1.4
Dominant language
Ruby
Stars
1.4k
Forks
472
Avg merge
1d 3h
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from twilio/twilio-ruby

All issues in twilio/twilio-ruby

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.