Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RapidPro chatbot channel - 500 from IoGT when RapidPro sends message #1575

Closed
sheralim012 opened this issue Mar 14, 2023 · 1 comment · Fixed by #1577
Closed

RapidPro chatbot channel - 500 from IoGT when RapidPro sends message #1575

sheralim012 opened this issue Mar 14, 2023 · 1 comment · Fixed by #1577

Comments

@sheralim012
Copy link
Contributor

Currently, we are using "IntegerField" for rapidpro_message_id in the Message model, it can only hold numbers between this range -2,147,483,647 to 2,147,483,647.
An error is raised when we try to put a value outside this range.
Use "BigIntegerField" instead which has a lot more range -9223372036854775808 to +9223372036854775807. And this is the default in newer versions of Django for primary keys.

@istride istride changed the title Use "BigIntegerField" for rapidpro_message_id RapidPro chatbot channel - 500 from IoGT when RapidPro sends message Mar 15, 2023
@istride
Copy link
Contributor

istride commented Mar 20, 2023

The message IDs that RapidPro sends back to IoGT are much larger than can fit in the IoGT database. The solution is to migrate the message ID field from IntegerField to BigIntegerField.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants