standup-tiered

# Transcript: 2026-04-21

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

---

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

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

Yeah, sure thing. I was focused primarily on Rel AI 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 working 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 will potentially differ from the requester dashboard or the existing Rel AI, 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. And I merged the other two PRs that addressed specific tickets.

Then towards the end of the day, DR hit me up asking 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 concerns to add those notifications, so we could easily remove it if we get to implementing that PubSub system.

With all that, I merged Todd's PRs and deployed them, and hopefully I'll get out these two other PRs that I opened up yesterday in response to issues that TR reported. That's me. How about you, Todd?

Yeah, good, but I am still dealing with permissions. They're not allowing me to actually see the admin or navigate to it. I can't get there. I'm hitting Continue with Salesforce, and then I'll address whatever that thing you were talking about there, Cam. 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.

The struggle continues, but hopefully this morning I'll get those permission sets set up. I'm getting real permissive right now. Salesforce is being Salesforce, and I've just been trying to debug and figure out why I've lost my Lightning App building permissions—the REST resource, or whatever it's called—to actually kick off the job on its own. If I can figure this out with Salesforce, that would kind of be the end of the functionality. But I don't know, so that's what I'm doing. My goal is to get the gateway open or remove the gate to syncing of those PRs.

I went back to Salesforce and added one more ticket.

Cool, thanks.

Okay, I'm catching up from yesterday. Thanks again for handling 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 of jobs that should be deleted—if you're thinking like this should all be deleted, just delete the code. Error on the side of deleting. Remember, git is forever, and we can always go back and get code from history if we need to.

So I did send a few back saying yeah, just delete this and so forth. I noticed some recent re-indexing and relationships jobs around uniqueness. I'm going to put up something here to add unique management for that because I'm playing around with wrangler right now, just keeping an eye on things. I'm trying to figure out—it looks like I'm missing some problems here.

I'm keeping an eye on the Salesforce indexing stuff. We got 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.

The other piece is that we're looking up the website and we don't have the right index on the website, and then doing a lookup at the root level.

I have all the designs ready, and I'm just kind of deep diving on them to get them tightened up. The company page—just to finish QA there and hand that off. 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. Yeah, optimistically tomorrow, latest Thursday or Friday.

Okay, this feels like something David's going to be persnickety about. I don't know why he just tends to have opinions. This feels like something he'll review today too.

Yeah. Okay. Sounds good. Cool. Um, okay, everybody. Does everybody have what they need? Everybody good?

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, but I just want to get your input first.

**System Audio:**
I actually went back and saw the admin page, which is in the list. If I can figure this out next time, I don't know, but that's what I'm working on. My goal is to get these companies handled, and that would be the next PR that goes into the dev branch. That would kind of be the end of that functionality. But with Salesforce, I have no idea what happens next. 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 testing.

I'll continue with Salesforce, and then I'll address whatever that thing you were talking about there, Cam. So that's it for me.

I'm going to catch up from yesterday. Thanks again for dropping the notifications. I got a bunch of messages about that too, so I would take care of it, but patience isn't always the best approach. We need to delete this code, clean up our entire code environment. I did send a few messages back saying, yeah, just delete this and so forth. I noticed things that need to be cleaned up, so if you can take care of that. You have to work really hard to actually delete code from the history. But if we need to, we can always go back and get it. There are some things that don't delete the code. We just want to delete the code.

I'm working with Sidekick Q Wrangler right now, just keeping an eye on things and trying to figure things out. It looks like I missed some recent re-indexing of relationship jobs, and that's causing some problems. I'm feeling pretty 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. I'm sending them your way. They should be relatively quick to take care of. I'm pausing the enrichment stuff and just waiting to keep an eye on the Salesforce and indexing stuff.

Todd, I'm going to send something your way. There's some shit that just makes sense. I'm feeling pretty good about things over here. I've been seeing this shit for six, eight months, but that H12 error keeps popping up in production. I'll send it your way. We're working on making the company lookup for the website faster, but probably not actually a win quite yet. So we just want to take care of that.

When you're ready, let's look at the other pieces. I'm trying to figure out what my next steps are. I have the target companies page, the settings pages, and the relationship pages all designed, and I'm just deep diving on them to get them tightened up. In addition to that, we're looking at the root of the website, but we don't have a column for that either, so it's just doing a sequential table.

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

I think David's going to have strong opinions about this. 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. But I want to get through this with you first. This feels like something David's going to be persnickety about. I don't know why, but this feels like something. Alright, everybody have a good day, guys. Talk soon.

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

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

Oh, it's a walk time! You gotta go! Amen. Here, come on.

The Monday standup covered three main workstreams: Ken is wrapping up Rel AI filters (addressed Michael's feedback, aiming for release by Thursday at latest), Todd is stuck debugging Salesforce Lightning permissions blocking his company sync PR, and Cam is triaging production issues including an H12 error caused by missing database indices on website lookups. Cam approved and merged several PRs, pushing the team to aggressively delete dead code rather than comment it out. A review session with David is planned for tomorrow around the filter UI/UX, as he's expected to have strong opinions on search and filter behavior. Design work on the company page, settings pages, and relationship pages is nearly ready for handoff.