standup

8:00 AM - 8:33 AM PDT · 2 blocks

haikusonnetopusPlatypus

Executive Summary

The Monday morning sync covered three main workstreams: Ken is nearing completion on RAI filters with some UI/UX polish remaining and an optimistic release target of Tuesday but possibly Thursday/Friday. Todd continues battling Salesforce permission issues that are blocking his ability to access the admin area and kick off jobs via the REST API, with a goal of getting his PR into the dev branch today. Cam identified a production H12 error caused by missing database indices on the website lookup table, assigned index fixes to the team, and is deep-diving on designs for the company page, target companies, settings, and relationship pages. A review session with David is being scheduled (likely tomorrow) to go over the RAI filter work before release, as he's expected to have strong opinions on search and filter behavior.

Mind Map

mindmap
  root((April 21 Sync))
    RAI Filters
      Ken primary owner
        UI/UX polish remaining
        Michael reviewed in 1:1
      Release timeline
        Optimistic: Tuesday
        Latest: Thursday/Friday
      David review needed
        Strong opinions on search/filters
        Session likely tomorrow
    Salesforce Integration
      Todd blocked on permissions
        Lost Lightning app building perms
        Cannot access admin area
      REST API needed to kick off jobs
      PR target: dev branch today
    Production Issues
      H12 error
        Missing indices on website lookup
        Sequential table scan on company lookup
        Fixes assigned to Todd
      Notification issues
        DR flagged connector dashboard gaps
        Missing notification setup
        Easy to remove when PubSub implemented
    Code Cleanup
      Cam sent PRs back for deletions
        Remove unused jobs
        Git preserves history
      Re-index jobs causing problems
      Unique constraints needed
    Design Work
      Company page QA
      Target companies page
      Settings pages
      Relationship pages
      

Action Items

RAI Filters Release

Production Fixes

Salesforce Integration

Code Cleanup

Design & QA

Notifications

Pipeline: haiku cleaned 2 blocks. opus synthesized the assembled transcript into structured insights.
haiku — Cleaned Transcript haiku
# Transcript: 2026-04-21

> 2 time blocks from 8:00 AM to 8:33 AM

---

### Morning work sync with Ken
**8:00 AM - 8:10 AM PDT** | *meeting*

**Microphone:**
Hey, Ken. Good morning. Thanks for handling these balls out yesterday.

Yeah, sure thing. I was focused primarily on RAI filters. I had a couple of issues that Michael took a look at during our one-on-one that I needed to address. So I spent the day sort of banging on that. And ultimately, I'm pretty satisfied with the results.

There's probably just a couple things that need to get sorted out as far as the UI and UX, but generally speaking, I think the user experience might potentially differ from the requester dashboard or the existing RAI, but we can discuss that later.

After that, I took a look at some of Todd's PRs. I left a comment on one of them—just a line that might have been missed as a cue. And I merged the other two PRs that addressed specific issues.

And then towards the end of the day, DR hit me up asking some questions about notification issues related to the connector dashboard. I took a look, and it looked like there might be some places where we were missing the setup to add those notifications, so we could really easily remove it if we get to implementing that PubSub system.

But with all that, the rest of Todd's PRs were merged and deployed, and then hopefully I'll get out the other two PRs that I opened up yesterday in response to what TR reported.

That's me. How about you, Todd?

Yeah, good, but I am still struggling. Permissions are not allowing me to actually see the admin area or navigate to it. I'm continuing with Salesforce. And then I'll address whatever that thing you were talking about there, Cam. So that's it for me. But I don't know—we'll see what happens. I'm going to get that PR into the dev branch today for sure, though, because that's kind of the last thing I need to do. So the struggle continues, but hopefully this morning I'll get those permission sets set up. I'm getting real frustrated right now. Salesforce is being Salesforce, and I've just been trying to debug or figure out why I've lost my Lightning app building permissions. I need the REST API, or whatever it's called, to actually kick off the job on its own. And then that would kind of be the end of functionality. But Salesforce—if I can figure this out, I don't know. So that's what I'm doing. That's my goal: to get the gateway or remove the gate to syncing those little PRs. I went back to Salesforce and added one more ticket.

Cool, thanks. Okay, I'm catching up from yesterday. Thanks again for dropping the notifications. I'm so glad those got taken care of. I've approved all PRs. Todd, I did send one back with changes. You had noted there were a couple jobs that were like, "Yeah, we're going to use this mostly," but we should delete this code if you're thinking like this is all going to be deleted anyway. Just error on the side of it—remember, Git is forever. Code stays in history, so if we need to, we can always go back and get it. If there are ways to continue to clean up our entire code environment, I did send a few back saying to just delete this and so forth. So if you just might take care of recent re-indexing and recent relationship jobs and uniqueness, I have to put up a fix here to add unique constraints because that's something I'm playing with Wrangler right now—just keeping an eye on things. And I'm trying to figure out if we missed some problems. This is a call by enrichment staff, and I'm just waiting to keep an eye on the Salesforce indexing stuff.

Salesforce returned an H12 error. We forgot some indices and some other things on the website lookup. So I'm sending them your way. They should be relatively quick to take care of. Beyond that, the response time is essentially what it is. What's happening is we're looking up the website and we don't have the right index on the website, and then it's just taking a long time to root through it. So that's the other piece. I have all these designs, and I'm just kind of deep diving on them to get them tightened up for the company page to finish QA there and hand off.

Okay, okay, cool. And Cam, it sounds like we're going to be in a filter release place in the next couple days, definitely this week, but maybe tomorrow could be Thursday now?

Yeah, optimistically tomorrow, latest Thursday or Friday.

Okay, this feels like something David's going to be persnickety about. I don't know why, but this feels like something we need to set up some time to review with him today too.

Yeah, okay. Sounds good. Cool. Um, okie dokie. Everybody have what they need? Everybody good?

Mm-hmm. He's going to have strong opinions about it. He tends to have strong opinions around search and filters and stuff. So I'll be setting up some time to review with him and you probably tomorrow then. But just to get through you and me first.

**System Audio:**
Yeah, good, those little PRs. I went back and actually saw the admin page, which is in the list, but next time if I can free this out, I don't know. So that's what I'm doing. My goal is to get to companies. And that would be the next PR that will go into the dev branch. And then that would lead to kind of the end of functionality. But as for Salesforce, I have no idea. I don't know, we'll see what happens. I want to get that PR into the dev branch today for sure because that's kind of like branch-possible testing. Continue with Salesforce. And then I'll address whatever that thing you were talking about there, Cam.

OK, I'm going to catch up from yesterday. Thanks again for dropping the notifications. I too got a bunch of messages about that, so I would take care of it, but patience is not always the best, I guess. I don't use this job anymore. Delete this, delete the code. When we can, we want to continue to clean up our entire code environment. So I did send a few back saying yeah, just delete this and so forth that I noticed. So if you could just take care of that. And you have to really work hard to actually delete code from the history. So if we need to, we can always go back and get it. There are some super connectors that don't delete the code. We just want to delete the code.

I'm playing Sidekick Q Wrangler right now, just keeping an eye on things and trying to figure it out. It looks like I missed some recent re-index jobs that are just causing some problems. Feeling real good about that call, by the way, guys. We have a Salesforce H12 error. We forgot some indices and some other things on the website lookup. So I'm sending them your way. They should be relatively quick to take care of. Pause the enrichment stuff and just wait to keep an eye on the Salesforce and indexing stuff. Also Todd, I'm going to send your way some shittiness. It just kind of makes sense. And feeling real good over here about for some reason just saying for several, you know, six months, eight months. But that's the H12 that keeps popping up in production. I'll send it. We're looking faster or making the lookup, the company lookup for website probably not actually a win quite yet. So we just want to take care of it.

And then otherwise, when you're ready, let's look at another piece. I'm trying to figure out what my next steps are. We have the target companies page, the settings pages, relationship pages. I have all designed and I'm just kind of deep diving on them to get them tightened up. Then additionally, we're doing a look at the root of the website, but we don't have a column for that either. And so it's just doing a sequential table.

It sounds like you're aiming for a release date for the Salesforce stuff this week?

Thank you. Okay, cool. I think he's going to have strong opinions about this. He tends to have strong opinions around like search and filters and stuff, so I'll be setting up some time to review with him and you probably tomorrow then, but just I want to get through you and I. Okay, this feels like something David's going to be persnickety about. I don't know why, he just feels like he would have opinions about something. Um, okie dokie. Everybody, have a good day guys. Talk soon.

### Brief chat before dog walk
**8:32 AM - 8:33 AM PDT** | *casual*

**Microphone:**
Yeah, yeah. However, they wanted to be profitable.

It's walk time, you gotta go! Amen. Come on.
opus — Synthesis opus
The Monday morning sync covered three main workstreams: Ken is nearing completion on RAI filters with some UI/UX polish remaining and an optimistic release target of Tuesday but possibly Thursday/Friday. Todd continues battling Salesforce permission issues that are blocking his ability to access the admin area and kick off jobs via the REST API, with a goal of getting his PR into the dev branch today. Cam identified a production H12 error caused by missing database indices on the website lookup table, assigned index fixes to the team, and is deep-diving on designs for the company page, target companies, settings, and relationship pages. A review session with David is being scheduled (likely tomorrow) to go over the RAI filter work before release, as he's expected to have strong opinions on search and filter behavior.

Transcript

8:00 AM - 8:10 AM PDTMicrophone
Hey, Ken. Good morning. Thanks for handling these balls out yesterday.
8:00 AM - 8:10 AM PDTMicrophone
Yeah, sure thing. I was focused primarily on RAI filters. I had a couple of issues that Michael took a look at during our one-on-one that I needed to address. So I spent the day sort of banging on that. And ultimately, I'm pretty satisfied with the results.
8:00 AM - 8:10 AM PDTMicrophone
There's probably just a couple things that need to get sorted out as far as the UI and UX, but generally speaking, I think the user experience might potentially differ from the requester dashboard or the existing RAI, but we can discuss that later.
8:00 AM - 8:10 AM PDTMicrophone
After that, I took a look at some of Todd's PRs. I left a comment on one of them—just a line that might have been missed as a cue. And I merged the other two PRs that addressed specific issues.
8:00 AM - 8:10 AM PDTMicrophone
And then towards the end of the day, DR hit me up asking some questions about notification issues related to the connector dashboard. I took a look, and it looked like there might be some places where we were missing the setup to add those notifications, so we could really easily remove it if we get to implementing that PubSub system.
8:00 AM - 8:10 AM PDTMicrophone
But with all that, the rest of Todd's PRs were merged and deployed, and then hopefully I'll get out the other two PRs that I opened up yesterday in response to what TR reported.
8:00 AM - 8:10 AM PDTMicrophone
That's me. How about you, Todd?
8:00 AM - 8:10 AM PDTMicrophone
Yeah, good, but I am still struggling. Permissions are not allowing me to actually see the admin area or navigate to it. I'm continuing with Salesforce. And then I'll address whatever that thing you were talking about there, Cam. So that's it for me. But I don't know—we'll see what happens. I'm going to get that PR into the dev branch today for sure, though, because that's kind of the last thing I need to do. So the struggle continues, but hopefully this morning I'll get those permission sets set up. I'm getting real frustrated right now. Salesforce is being Salesforce, and I've just been trying to debug or figure out why I've lost my Lightning app building permissions. I need the REST API, or whatever it's called, to actually kick off the job on its own. And then that would kind of be the end of functionality. But Salesforce—if I can figure this out, I don't know. So that's what I'm doing. That's my goal: to get the gateway or remove the gate to syncing those little PRs. I went back to Salesforce and added one more ticket.
8:00 AM - 8:10 AM PDTMicrophone
Cool, thanks. Okay, I'm catching up from yesterday. Thanks again for dropping the notifications. I'm so glad those got taken care of. I've approved all PRs. Todd, I did send one back with changes. You had noted there were a couple jobs that were like, "Yeah, we're going to use this mostly," but we should delete this code if you're thinking like this is all going to be deleted anyway. Just error on the side of it—remember, Git is forever. Code stays in history, so if we need to, we can always go back and get it. If there are ways to continue to clean up our entire code environment, I did send a few back saying to just delete this and so forth. So if you just might take care of recent re-indexing and recent relationship jobs and uniqueness, I have to put up a fix here to add unique constraints because that's something I'm playing with Wrangler right now—just keeping an eye on things. And I'm trying to figure out if we missed some problems. This is a call by enrichment staff, and I'm just waiting to keep an eye on the Salesforce indexing stuff.
8:00 AM - 8:10 AM PDTMicrophone
Salesforce returned an H12 error. We forgot some indices and some other things on the website lookup. So I'm sending them your way. They should be relatively quick to take care of. Beyond that, the response time is essentially what it is. What's happening is we're looking up the website and we don't have the right index on the website, and then it's just taking a long time to root through it. So that's the other piece. I have all these designs, and I'm just kind of deep diving on them to get them tightened up for the company page to finish QA there and hand off.
8:00 AM - 8:10 AM PDTMicrophone
Okay, okay, cool. And Cam, it sounds like we're going to be in a filter release place in the next couple days, definitely this week, but maybe tomorrow could be Thursday now?
8:00 AM - 8:10 AM PDTMicrophone
Yeah, optimistically tomorrow, latest Thursday or Friday.
8:00 AM - 8:10 AM PDTMicrophone
Okay, this feels like something David's going to be persnickety about. I don't know why, but this feels like something we need to set up some time to review with him today too.
8:00 AM - 8:10 AM PDTMicrophone
Yeah, okay. Sounds good. Cool. Um, okie dokie. Everybody have what they need? Everybody good?
8:00 AM - 8:10 AM PDTMicrophone
Mm-hmm. He's going to have strong opinions about it. He tends to have strong opinions around search and filters and stuff. So I'll be setting up some time to review with him and you probably tomorrow then. But just to get through you and me first.
8:00 AM - 8:10 AM PDTSystem Audio
Yeah, good, those little PRs. I went back and actually saw the admin page, which is in the list, but next time if I can free this out, I don't know. So that's what I'm doing. My goal is to get to companies. And that would be the next PR that will go into the dev branch. And then that would lead to kind of the end of functionality. But as for Salesforce, I have no idea. I don't know, we'll see what happens. I want to get that PR into the dev branch today for sure because that's kind of like branch-possible testing. Continue with Salesforce. And then I'll address whatever that thing you were talking about there, Cam.
8:00 AM - 8:10 AM PDTSystem Audio
OK, I'm going to catch up from yesterday. Thanks again for dropping the notifications. I too got a bunch of messages about that, so I would take care of it, but patience is not always the best, I guess. I don't use this job anymore. Delete this, delete the code. When we can, we want to continue to clean up our entire code environment. So I did send a few back saying yeah, just delete this and so forth that I noticed. So if you could just take care of that. And you have to really work hard to actually delete code from the history. So if we need to, we can always go back and get it. There are some super connectors that don't delete the code. We just want to delete the code.
8:00 AM - 8:10 AM PDTSystem Audio
I'm playing Sidekick Q Wrangler right now, just keeping an eye on things and trying to figure it out. It looks like I missed some recent re-index jobs that are just causing some problems. Feeling real good about that call, by the way, guys. We have a Salesforce H12 error. We forgot some indices and some other things on the website lookup. So I'm sending them your way. They should be relatively quick to take care of. Pause the enrichment stuff and just wait to keep an eye on the Salesforce and indexing stuff. Also Todd, I'm going to send your way some shittiness. It just kind of makes sense. And feeling real good over here about for some reason just saying for several, you know, six months, eight months. But that's the H12 that keeps popping up in production. I'll send it. We're looking faster or making the lookup, the company lookup for website probably not actually a win quite yet. So we just want to take care of it.
8:00 AM - 8:10 AM PDTSystem Audio
And then otherwise, when you're ready, let's look at another piece. I'm trying to figure out what my next steps are. We have the target companies page, the settings pages, relationship pages. I have all designed and I'm just kind of deep diving on them to get them tightened up. Then additionally, we're doing a look at the root of the website, but we don't have a column for that either. And so it's just doing a sequential table.
8:00 AM - 8:10 AM PDTSystem Audio
It sounds like you're aiming for a release date for the Salesforce stuff this week?
8:00 AM - 8:10 AM PDTSystem Audio
Thank you. Okay, cool. I think he's going to have strong opinions about this. He tends to have strong opinions around like search and filters and stuff, so I'll be setting up some time to review with him and you probably tomorrow then, but just I want to get through you and I. Okay, this feels like something David's going to be persnickety about. I don't know why, he just feels like he would have opinions about something. Um, okie dokie. Everybody, have a good day guys. Talk soon.
8:32 AM - 8:33 AM PDTMicrophone
Yeah, yeah. However, they wanted to be profitable.
8:32 AM - 8:33 AM PDTMicrophone
It's walk time, you gotta go! Amen. Come on.