---
title: "Three overnight jobs hit the same 5:30am session limit while the other seat sat idle"
canonical: https://dxdev.com/blog/multiple-seats-spending-strategy/
datePublished: 2026-09-14
---
At 2:41 in the morning, one of our automated helpers came back with six words: "You've [hit your session limit](/blog/claude-pool-identity-binding-and-generation/), resets 5:30am." An hour later a completely different job hit the identical wall. An hour after that, a third one did too. Three separate pieces of overnight work, three timeouts, one shared clock ticking down to 5:30 America/New_York.

## How the seats were supposed to work

We run a handful of paid AI subscriptions. Each one is a "seat," each seat has a usage cap, and the cap refills on a schedule, like a data plan that tops off at a set hour every day. The idea is that if one seat is busy, the work goes to the other one instead of stalling until morning.

That night it didn't work. Everything piled onto one seat and burned through its whole daily cap three times before sunrise. The second seat had room to spare, and nothing was routed to it.

## The diagnosis, which took until almost 4pm

We didn't find out why until almost 4pm that day, after two other people's tickets and an installer bug in one of our coding tools ate the front half of it. The login on our main seat had been overwritten with a different account, our own second account, during some earlier setup work. There was no breach. A credential got swapped during an earlier reconfiguration and nobody caught it, because both accounts logged in fine and neither one threw an error.

From the outside it looked like one very overworked seat and one idle one. In fact one seat was doing the job of two, and the other had been misconfigured to look busy when it wasn't.

We filed it as a low-priority ticket. Nothing was costing money that minute, so we deliberately left it for the next full stop-and-review session instead of dropping everything to chase it. That's a call small businesses make constantly: is this urgent, or just annoying? We called it annoying, and it cost us a night.

While sorting out which login belonged where, we went back and checked what each seat's plan was rated for, instead of assuming. We had been treating the second seat as roughly a "5x" plan, the smaller of two usage tiers we'd signed up for at different times. It was actually rated for "20x," a much bigger daily allowance that had sat almost entirely unused because nothing had ever been pointed at it on purpose.

So we had four times the overnight capacity available and had been rationing work as if we didn't.

## Asking the wrong question

When you pay for more than one AI subscription, the instinct is to ask "which one is cheaper per task" or "which model is smarter." Neither was the question that mattered here. The one that cost us three failed jobs and a night of nothing running was this: which seat is closer to its refill time, and does it have good work lined up for the moment it refills? A seat with four times the daily room does you no good if the work keeps landing on the smaller one out of habit, or by accident, the way ours did.

## The fix was bookkeeping

We wrote down, in the same place we track everything else, which login belongs to which seat, what each one's real daily cap is, and what time each one resets. When a job is queued and one seat is about to run dry, it goes to whichever seat has room and is closer to reset, not whichever one it has always used. It's the same logic as making sure your busiest cashier isn't also the one who went on break first.

## What it cost

The three failed jobs weren't expensive on their own. They meant a few minutes of retrying and nothing that showed up on an invoice. The real cost was a full night where automated review work that should have kept moving just stopped. Nobody noticed until the next afternoon, because the failure looked like ordinary quota exhaustion instead of a login pointed at the wrong account.

If you run more than one AI seat, pull up each subscription, confirm which login is attached to which one, and check its real daily limit against what you assumed.