Team, I just got off the phone with Dustin, who is PAUSING whatever he can before he comes into the office
Prior to that, just got off the phone with LR and we have been 'abusing' them since yesterday, outside of the times and thresholds allowed
Please LMK what it is that we added/changed yesterday so we can have a FULL understanding of what/why that is
and in the meantime STOP anything outside those thresholds and ANYTHING not absolutely NECESSARY "right now" or we are going to get blocked again!
@here no changes by me or contact center leaders.
12/17/2024 I added a second account to the lr_data dump function Nothing Integration wise has changed I will be on site in about 25 minutes
Apparently it was Aidan
We haven’t used what originally caused the first shutdown. We have been running normal campaigns and backfilling some. A better definition/understanding of what “abusing them” is would be appreciated. There has not been any information relayed to us about what that threshold to be considered “abuse” we can try to avoid that if we understand it better.
I need everyone that touches this stuff, regardless of why to FULLY understand that we can NOT just do whatever, and if there are changes like that, to adding to requests/traffic they need to be evaluated before executing and absolutely within those thresholds and time that LR has given us. otherwise they will block us first and ask questions later
I am trying to get the details, they couldn't get me info from yesterday
The endpoints that are being pulled are: Getcasesummery Getlead Getcontact
Ok that is fair we can send you the expected load every day of what we are attempting to send. You and LR can then let us know if we have to limit anything. We can turn off all automations and run batches but that will get backlogged and clients won’t receive things “real-time” . Also, all the financial queries from Ryan will have to be limited as well, and we would have to not let any adhoc reporting happen without approval from LR. This will affect the dashboard for both cam and clients too.
Noted - Do we have an document/inventory/list of all of these items that the team(s) can be aware of ? if not please create and share ASAP, thank you!
We can put together a list regarding integrations, we will need to go around to account for all other departments, and I’ll need to talk with Ryan about limiting the financial run frequency.
Thanks, once we know what those all are, we can priorate by need and weight on system load/traffic
@Nick Ward can you look into if any of the reports on your side are using an API and then we can add all of them together into a shared sheet/doc for Joe and LR?
After discussing with Aidan to get an idea what was previously run, he mentioned that he is using getcustom report, getintakecontact and setanswer this morning. However prior to today he was using getcasesummary and getcustomreport. Moving forward we will follow the instructions that is mentioned above within the chat to ensure we are don't hit those limits and if it is possible if we can receive more clarity on what those limits are that would be great since reporting team does use API to pull custom reports to update things live and daily
I’d be happy to assist in gathering a comprehensive list of departments I work closely with that utilize specific API scripts for Law Ruler. This will ensure we proactively address any potential issues and avoid a recurrence of similar challenges we faced in the past.
@Joe Santana we have expectations for some backfills and finalizations before year end. We may need to draft a reduced service email/script together so that some of the clients are aware they won’t be getting their leads until this is resolved. I would rather it come from leadership than from someone on the team in an off hand conversation about why they aren’t seeing leads. A lot of clients are looking to push things through before year end and if they ramp up more it will be a problem, may need to nip it in the bud.
I think that ultimately how it should be is our team are the only ones directly “integrating” with anything and all reports/dashes come from what has already been pulled into GCP. If any team needs something outside of that then they can submit it for review.
May be unrelated but Jackson told me about another issue, details are in the attached image
@Nicholas McFadden @Joe Santana @Nick Ward we can NOT be delayed in sending claimant data to law firms. This casues massive issues, results in greater fall out, unhappy law firms, loss of revenue. Please fix, we need permanent solution asap
@here Meeting invite will go out shortly for a quick meeting on the cause of LR APIs being hit hard.
Cam / All, The point was to stop anything outside the norm, clearly was ok to return to normal operations
Had quick meeting, moving forward, thank you Dustin / NickW
Cause: A script that updated leads combined with script to dump updated leads to database created a lot of API calls Action Items: • Dustin will add a email notification if too many leads are updated at once • There will be a policy of code review, QA & notification of any code that will touch an API
"too many" need a flagging point please, we talked about 2K but that seemed high.... but I am not sure at a processing, load, traffic transaltion