Customer problems in Karinderya! are easiest to solve when you identify the last completed stage. A customer may be waiting to sit, waiting to order, waiting for cooking, waiting for a finished plate, or waiting for payment and table reset. Community pages show a runaway or unpaid-customer alert, but checked official text does not publish its exact cause, timer, recovery control, or penalty.
Customer will not sit
Confirm that a complete table-and-chair set exists and is not already occupied or unfinished. Clear decoration around the chair, rotate or move the set, and walk the route from the entrance. Use the visible assignment interaction and wait for the state to update.
If one set works and another does not, copy the spacing of the working set. Do not buy more furniture until access is repaired. A visual empty seat is not usable capacity when the prompt or path is blocked.
In co-op, assign one front-of-house player to seat customers so two people do not repeat the same interaction while another table waits.
Customer waits for food
Read the order again. Confirm the recipe is available, ingredients are stocked, a stove can accept it, and the finished plate has not already appeared. Trace the dish from request to station to collection rather than assuming the kitchen needs more equipment.
The cooking and orders guide provides a full queue-recovery sequence.
Runaway or unpaid alert appears
Note which table and service stage were involved. Community guides associate the alert with a customer leaving without paying, but sources disagree or remain unclear about exact timing and recovery behavior. Do not promise that chasing, clicking, or using a particular object always restores payment.
Prevent repetition by shortening the stage that waited. Repair seating access, stock the requested dish, reduce simultaneous customers, collect finished plates, or complete table interactions promptly. If the alert follows one specific table, test that route with a single customer.
Avoid expanding after a failure. More seats multiply the same pressure. Restore several complete cycles first and observe whether the alert returns.
Customer or table appears stuck
Finish nearby prompts and allow the server to update. Move close enough to the likely interaction side, clear newly placed objects, and avoid rapid repeated inputs. Another player may have changed the state in co-op.
If payment or clearing remains unfinished, keep the table out of your capacity count until it resets. Work with functioning tables rather than placing new customers around a stuck object.
When several unrelated interactions stop responding, record current cash and tasks, then rejoin a fresh server if safe. A server issue should be ruled out before rebuilding a working layout.
Prevent problems through capacity control
Seat only as many customers as the kitchen and team can finish. Add one table set at a time. Keep ingredient reserves for the active menu. Use all supplied stoves before buying another. Maintain an open service lane and assign clear co-op roles.
Watch the oldest queue for several cycles. When it shifts from seating to cooking or serving, adjust the next improvement. The progression hub connects these signals to spending and five-star readiness.
Customer health is more useful than room fullness. A smaller restaurant completing payments consistently can fund safer growth than a crowded room producing alerts.
Incident recovery routine
Pause new assignments, collect ready plates, deliver known orders, finish payment or clearing, check ingredients, and reopen one tested table. Serve one full customer cycle. Then change only the stage that failed and compare a few more customers.
This routine does not rely on an unpublished timer or penalty formula. It restores the dependency chain and produces a clear next decision for your restaurant.