- Duration: 18 min
- Platform: zoom
- Source: Read.ai 01JAWZRPEGYFP4N0CDEQEE2W99 (https://app.read.ai/analytics/meetings/01JAWZRPEGYFP4N0CDEQEE2W99)
Transcript
[UNKNOWN_SPEAKER]: Hey, how are you doing? Okay. [Rafael Bruno]: How about you? [Michael Houck]: Yeah, I’m doing okay. Let’s give Sid a minute here. [UNKNOWN_SPEAKER]: Sure. [Michael Houck]: Okay, I’m not sure where Sid is. I’m going to message him. [Sid]: Night. Hi guys, sorry for late. I was actually sending a message to Rafael for a call. So I got occupied with that. [UNKNOWN_SPEAKER]: All good. [Michael Houck]: I have another call at the 1240, 1145. So let’s just jump through this. So, okay. Give me a sense. I guess let’s just go one by one and let’s try to go quickly. So Sid, we’ll start with you for 940 follower growth track. What’s the blocker there? [Sid]: No, I don’t have any blockers there. That ticket is actually going good. I, I mean, I fixed it earlier, but there was still an issue. So I, I, I’m checking with that one. Why, what needs to be done? So I’m checking the API logic and we’ll be fixing that once I get the issue. So that I’m trying to replace it on local. [Michael Houck]: Is the issue with. The data being imported wrong or is the data is the issue with how the data is being represented on the dashboard? [Sid]: That’s right. The issue is with how we are fetching the data. The importing is fine. There’s no issue with that. The APL logic that we have written, I need to dive deeper into that and fix the issue. Find the issue and fix it there. Okay. [Michael Houck]: Yeah, I mean, it should be pretty straightforward. It’s just what’s the most recent number versus the number at the beginning of the period that they use is looking at, right? So nothing too complex there. [Sid]: Yeah, I mean, it’s straightforward. I’m just working on that one should be completed in a bit. [UNKNOWN_SPEAKER]: And yeah. Anything else? And what? [Michael Houck]: I mean, not on that. [Sid]: And then I’ll be moving to other tickets. So 898 is done just giving an update. 898 is completed. I just need to check with Rafael on how we how we are doing it. That said, and then there’s is 929. For that, Rafael mentioned what we have to do, but I need to get some more context because that is the target I need to work with Rizwan. So I do whatever we need to do on my part, but I just need to be in sync with what Rafael is thinking. [Michael Houck]: Sorry, I’m confused on that one. Isn’t that one just importing the photos to S3 and displaying them on the dashboard? [Sid]: For that one, Rafael mentioned that we will be using we will be using Kafka and we need to emit some messages to Kafka for each account. So if there are 3,000 accounts, we need to log message to Kafka. And then there is one on the other side, we take care. [Rafael Bruno]: Let me summarize the problem. The first way that Sil was trying to import the data was not working correctly. So the idea is to just tell the scraper to get all the photos again. [UNKNOWN_SPEAKER]: Oh, got it. [Michael Houck]: Oh, that’s interesting. Okay, I guess that works. But why can’t we just import the photos? For some reason, it was not the way that we are importing was not working. [Rafael Bruno]: Okay. [Sid]: So the thing is, the logic was written properly, it was working, but for the first couple of records, it worked. But after that, it started giving error that the URL that account URL is expired. So it has a very short validity of a couple of minutes only. And that is why it was failing. So what we did is we switched all 3,000 accounts first. And let’s say that the validity was just 10 minutes. And when we were running that logic in batches, probably that limit, that expiry was over by the time, like in 10 minutes. And we got that error. [Michael Houck]: So that’s why we are doing it this way. But why do we need some expiring URL? Don’t we know what account each photo is related to already from Airtable? [Rafael Bruno]: What Sid was trying to explain is that when he was trying to fetch the URL of the photos on Airtable, for some, he was able to do that. But for others, Airtable gave us URL that expired. So he was not able to fetch the data. Okay. [Michael Houck]: I mean, fair enough. I guess let’s just run the scraper then and recollect them. That’s fine. Okay. Sid, and then the last one for you is 920. This is the creator payouts weren’t processed and referral earning data wasn’t correctly imported, mostly about the referral data. So was this Was this fixed? Is this done? [Sid]: So I will be working with Rafael on this one. So I put this, I mean, meanwhile, I’m fixing other issues and then we’ll come to this one. [Michael Houck]: Okay, but it’s in review. [Sid]: So why is it in review if there’s still work to be done on it? [Michael Houck]: It looks like I changed it to interview six days ago. I don’t know what that’s regarding. But it’s been in review for six days. [Sid]: So we haven’t worked on it in six days. No, no, no. We were working on the charges. The thing is before this is done, we need to fix the charges and other things, and then we can come to this. So we fixed, I think Rafael, we fixed charges yesterday. Okay. [Rafael Bruno]: So now that it’s been fixed, now we can work on this one. Before making the payout to those creators, we need to make sure that all the earnings is correct. So we want, give a wrong amount to them. So this is something that is blocked by one of my tasks. [Michael Houck]: Okay, sounds good. But it should be pretty quick once that’s done. Like it’s just processing the payouts, basically. Yeah, it just sends the money. Okay, cool. Okay, let’s move on to yours, Rafael. So 973, that’s the engagements incorrectly marked as missed. [Rafael Bruno]: About that task, I did the cleanup and I think I texted you that we have 10 broadcasts that had engagements that are wrong. I already passed those 10 broadcasts to RISC-I and RISC-I is working on them to figure out what went wrong. Regarding my part is done and the other part Rizwan is doing. [Michael Houck]: Okay, so we should expect that to be done today? [Rafael Bruno]: Yeah, I will text him to know where he is at and I’ll let you know. [Michael Houck]: Okay, I mean, if we need to just ask Rina to like give you a spreadsheet with the correct data and then just import that, Rizwan can keep solving. [Rafael Bruno]: We have the correct data. The thing that we don’t know is why the scraper produced the wrong data, but the correct data random. That makes sense. We can treat that as a separate task. [Michael Houck]: If the data is correct in the database, we can mark this as complete. [Rafael Bruno]: Okay, I’ll fix that on the database and I’ll mark that as complete. [Michael Houck]: Okay, and feel free to add a new task for RISC-I too, like related to this. Okay, just so we have a tract. Is there any chance that more than those 10 have been also wrong since we pulled those 10? [Rafael Bruno]: The thing that I’m comparing it with is the spreadsheet that Raina produced. So from all the engagements that we produced since the day that she was recording that, we only identified those 10 problems. [Michael Houck]: Was that done at a certain date, or is she still doing that every day right now? [Rafael Bruno]: I think that she’s still doing that because we have, let me find here. We have data from, we have data since the beginning of October, October 7th until today, basically. Okay, so she’s still doing it right now. [UNKNOWN_SPEAKER]: That’s fine. [Michael Houck]: Once Rizwan fixes that, let’s have Rina stop doing next. It’s not a good use of her time anymore. Fortunately for Confluent, all the bugs are solved. Okay. Okay, next one, 969. That’s the wallet data issue. So where are we at with that? [Rafael Bruno]: Yeah, this is the one that I’m working right now. I was able to successfully fix the charges problem, successfully fix the earnings problem, but the referral earnings problem, I’m still working on. I’m adapting the script to do that. After I finish this, then I will pass those scripts to Sid so he can append this past data with the new data on production. Got it. Okay. [Michael Houck]: I’m a little worried about timeline here because if you’re working on this right now, you know, Sid’s going to sign off for the day in a couple hours. Are we going to have to wait until tomorrow to do this or should you just take it on and whole thing today before. [Rafael Bruno]: I could do that, but I need a little help for Sid with the scripts that he used to concatenate the data from the existing table and the thing that we are changing. Okay, Sid, can you send that to Rafael somehow right after this call? [Michael Houck]: I just want to make sure this doesn’t linger for another day, so let’s all be assured. [UNKNOWN_SPEAKER]: Yeah, sure. [Sid]: I’ll catch up with him and give whatever he needs. [Michael Houck]: Okay. Rafael, next one. $7.96. This is blocked payments making it through onboarding. [Rafael Bruno]: I think that the other tasks are all related with payments or Stripe, right? Yep. Correct. I initiated those tasks. I was checking all the flows on Stripe and payments, but I was not able to finish that I will go back to those tasks after I finish the other two. Okay, I think that’s the right the right order of operations. [Michael Houck]: So let’s do that. Hopefully the other two are pretty quick today. But let me know where you get with the payment stuff after that. [UNKNOWN_SPEAKER]: Okay.