You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 23, 2024. It is now read-only.
Describe the bug
Hello. I'm using this tap to get SMS messages information to our postgres target. The problem is that a couple of weeks ago the taps failed to find a state file and start a full refresh of data unfortunately it got stuck on an infinite loop requesting pages.
I've checked our twilio panel and for March we've got about 170k messages, that should be extracted on over 3700 pages of 50 items. But currently the tap is still runing on Page 1700000 aprox and not stopping. If I run the API call request manually I see that the response is returning data and a next_page_uri. Based on the Pages and the 50 batch items amount it seems I should have more than 85 million records and that is impossible. I've already check with API call and Twilio Console and I have less than 170000 message records for March.
To Reproduce
Steps to reproduce the behavior:
Run the tap with 30 days window
Sample API call ```"next_page_uri": "/2010-04-01/Accounts/ACXXXXXXXXXXXXXX/Messages.json?DateSent%3E=2022-03-01&DateSent%3C=2022-03-31&PageSize=50&Page=1770548&PageToken=PASMXXXXXXXXXXXXX
Expected behavior
API Response should loop through all available pages and stop once completed.
Describe the bug
Hello. I'm using this tap to get SMS messages information to our postgres target. The problem is that a couple of weeks ago the taps failed to find a state file and start a full refresh of data unfortunately it got stuck on an infinite loop requesting pages.
I've checked our twilio panel and for March we've got about 170k messages, that should be extracted on over 3700 pages of 50 items. But currently the tap is still runing on Page 1700000 aprox and not stopping. If I run the API call request manually I see that the response is returning data and a next_page_uri. Based on the Pages and the 50 batch items amount it seems I should have more than 85 million records and that is impossible. I've already check with API call and Twilio Console and I have less than 170000 message records for March.
To Reproduce
Steps to reproduce the behavior:
Sample API call ```"next_page_uri": "/2010-04-01/Accounts/ACXXXXXXXXXXXXXX/Messages.json?DateSent%3E=2022-03-01&DateSent%3C=2022-03-31&PageSize=50&Page=1770548&PageToken=PASMXXXXXXXXXXXXX
Expected behavior
API Response should loop through all available pages and stop once completed.
Your environment
The text was updated successfully, but these errors were encountered: