Support follow-up on your connector query

Hi Ciaran, Following up on the ticket you raised earlier this week. I've had a look at the logs on our side and the sync that was lagging for one of your sources looks to have caught up. Records are loading again and the nightly refresh finished ahead of the usual time this morning. Two things I'd like to confirm before I close it: - Can you check the source is showing as healthy from your end? - Did anything change in the role grants on the Snowflake side recently? I can see a permissions warning in the logs that cleared on its own, and I'd like to know why. No rush on the second one, but it would help me write up the cause properly. Thanks, Ruth

Ruth, Checked. Source shows healthy and the record count has moved again. On the grants: I checked the role grants and nothing was changed on purpose. We did rotate a service role earlier in the week, so that's my guess for the warning. Which warehouse is that running on? If it's the shared one, I'd like to rule out a suspend/resume timing issue before I say it was the rotation. Ciaran

Hi Ciaran, Good question. It's running on the warehouse you set up for the B-Viz workload, not the shared one, so I don't think suspend/resume is involved. The warning lines up with the time the rotated role was picked up, which fits what you said. I can't see anything that suggests it was more than a short gap while the new role took effect. I've noted it that way on the ticket. If you can confirm you're happy with the explanation, I'll close it. It might also be worth adding a note to your own runbook so the next rotation doesn't surprise anyone, and I'm glad to send over what we saw in the logs for that. Thanks for the quick turnaround today. Best, Ruth

Ruth, Happy with that. Close it. Yes please to the log extract. I'll attach it to the runbook entry. Documentation the client can keep, and all that. That's a schema question for another day, but the next rotation will go in midweek with a note to you first. Ciaran