Overnight load follow-up
Email thread Kelbrook Mutual Insurance · support
Support thread: the claims source finished late because Kelbrook's claims team moved the scheduled export later. Tariq Mahmood chose to have the export brought forward. The ticket stays open while he checks the next few loads.
What was said
What this says
As at Fri 9 Oct 2026Support thread: the claims source finished late because Kelbrook's claims team moved the scheduled export later. Tariq Mahmood chose to have the export brought forward. The ticket stays open while he checks the next few loads.
Ask: Connor Webb asked Tariq to check for source-side changes. Tariq confirmed the claims team had adjusted the export, then asked Connor to confirm the cause rather than rely on his word.
Customer view: Tariq prefers the simple fix and will not touch mapping without telling Rebecca first. He is careful about member data in email.
Next: Tariq checks the next few loads and reports back. If runs are still late, the option of moving the claims load start comes back.
The thread
Updated 9 Oct 26Messages
Connor Webb 3 Mar 2025 12:37Hi Tariq, Following up on the ticket you raised about the overnight load. I've been through the logs for the last few nights and the claims source did finish, but later than the usual window on a couple of mornings. The policy and helpline sources look normal. I don't want to guess at the cause from our side, because it may well be something that changed in the source system rather than in B-Viz. Could you check whether anything was altered on the claims side recently, for example a new field, a renamed table or a change to the export schedule? If you can tell me what you find, I'll line it up against what I'm seeing and we can decide whether it needs a mapping change or something from our engineers. I haven't changed anything in your environment. Thanks, Connor Support Engineer, BG-Demo
Tariq Mahmood 6 Mar 2025 08:57Hi Connor, Thanks for the detail, and apologies for the slow reply. I'll check last night's load as well, and I did look at the claims side. Our claims team did adjust the scheduled export a little while ago, so the file lands later than it used to. That would fit what you describe, but I'd rather you confirm it than take my word for it. I haven't touched any mapping, and I won't without telling Rebecca first. Which member number is that on the late runs, if any were affected? I don't want to send anything over email that identifies a member, so just tell me how many records were involved and I'll look at them here. Thanks, Tariq- Connor Webb 7 Mar 2025 10:08Hi Tariq, That helps. Checking the timings, the late mornings line up with the later export landing, so the load was simply starting after the file arrived and running past its usual finish. No records were dropped or duplicated, and the data is complete as of this morning's run. Two options from here: - Ask your claims team to bring the export back earlier, so the nightly refresh is complete by 07:00 as normal. - Leave the export where it is and we look at moving the start of the claims load to follow it. The second would be a change on our side, and I'd want a colleague to review it before we do anything. Which would you prefer? Happy to jump on a short call if easier. Thanks, Connor
- Tariq Mahmood 7 Mar 2025 12:02Hi Connor, I've spoken to the claims team. They can bring the export forward, so let's try the first option. That keeps it simple and doesn't need any change to the load itself. I'll check the next few loads and let you know if anything is still running late. If it is, we can come back to the second option. You can leave the ticket open until then. Thanks, Tariq