[[misc]](/)|[[TIL]](/content/TIL.html) # Zoom Meeting ID storage Today I was asked by a friend for help with a strange database issue. There had been no changes to the code in over a week, but somehow today, all of a sudden, an issue arose that would not resolve itself. The application calls the zoom API to get a meeting id, and stores that meeting id in a postgres database. <img height=80% width=100% src="database-code.png" alt="Code showing db interaction" /> The first sign of trouble was made clear in sentry, with the application raising an exception that it was unable to book a meeting with the Zoom API. However, we were able to verify on the zoom side that meetings were in fact being booked. <img height=80% width=100% src="failed-to-book.png" alt="Zoom booking exception" /> Following that thread yielded another exception, this time indicating that there was an issue with performing a query while in the middle of a transaction. <img height=80% width=100% src="transaction-error.png" alt="Zoom booking exception" /> But the code hadn't changed, so why was this pattern suddenly prohibited? This error, too, turned out to be a red herring, as it was covering up the actual underlying issue. The new error seems to indicate that we were attempting to store a non-integer value in an integer field. <img height=100% width=100% src="out-of-range.png" alt="Exception showing integer out of range" /> I had initially thought it could be due to recent zoom security changes to add passwords to the meeting, but that was not the case. I verified that we were in fact storing the meeting id as an integer, and that was the only integer column in that table so it was likely that the meeting id was somehow malformed. Running out of ideas, I searched Google for "zoom api changelog" and lo and behold, they had _just_ changed their API to return meeting ids as type `long` versus type `int`. <img height=80% width=100% src="api-update.png" alt="API update" /> `:facepalm:` [](https://github.com/vagelim)