Guide
OGameX Bank Transfer Queue
The Queue subtab explains what Bank is trying to fund and what happened to each transfer. It shows request reasons, remaining resources, in-transit amounts, delivered amounts, expected arrival and return, and current status.
Overview
A request is created for a building or research requirement when Bank support for that category is enabled. Several reasons for the same destination can be grouped into one request. The request then moves through waiting, sending, arrival, and completion states.
Use the Queue to investigate a waiting Auto Build or Auto Research target before changing priorities or reserves. It is more informative than repeatedly selecting Run now.
Request Details
Reasons lists the building or research targets that created the requirement. Confirm that the labels and requested levels match the feature you intended to support.
Remaining is the amount still needed at the destination. In transit is already on a flight. Arrival reflects resources delivered or the expected arrival information, depending on current state. Return shows when cargo ships are expected back.
When multiple transfer batches are allowed, one request can have resources in transit while another amount remains. Do not assume partially sent means the target has enough to start.
Status Meanings
- Pending means the request is queued for consideration.
- Waiting for fleet slot preserves configured slot availability.
- Waiting for resources means the Bank source cannot currently supply the requirement while respecting reserves.
- Waiting for ships means allowed cargo capacity is unavailable.
- Waiting for pause avoids sending at an unsuitable time.
- Remaining indicates a partial transfer with more still required.
- Sent means a transfer flight was submitted.
- Arrival means delivered resources are being accounted for.
- Targets complete means the supported requirements no longer need the request.
- Cancel identifies a canceled request.
- Failed or retrying needs review before another attempt.
Status describes the Bank workflow, not the final building or research queue. After delivery, the dependent feature still makes its own decision.
Arrival and Return
A transfer occupies ships and a fleet slot until the return completes. Bank may wait before sending another request from the same source. Review both arrival and return times when coordinating expeditions, farming, Defender, or Pause Fleet Save.
Resources can arrive before ships return. The destination may start its target while the Bank source still lacks those cargo ships for another delivery.
If the displayed timing is past but the state has not updated, compare the actual movement in OGameX and allow the next normal check. Avoid creating duplicate manual transfers before the result is clear.
Canceling Requests
Use Cancel on a request that is no longer wanted. Canceling prevents remaining Bank work for that request, but it cannot recall a transfer already sent.
Before canceling, check whether resources are in transit. Then adjust the original Auto Build or Auto Research target or policy so an identical requirement is not immediately created again.
Clear completed removes finished history from the visible queue. Use it after reviewing results; it does not remove active or waiting work.
Investigating a Waiting Target
Follow this order:
- Confirm the request reason matches the expected target.
- Compare remaining and in-transit resources.
- Check the current status.
- Verify Bank source stock and minimum deuterium.
- Verify allowed cargo ships and free fleet slots.
- Check whether a pause is active or approaching.
- Review arrival and return before changing another module.
See the main Bank guide for source and policy settings and Daily Collection for surplus movement toward Bank.
Recommended Setup
- Create one small building or research requirement.
- Open Queue before the first Bank action.
- Verify the reason and destination.
- Watch pending become sent or a meaningful waiting state.
- Compare remaining and in-transit values.
- Confirm arrival in the game.
- Wait for cargo ships to return.
- Clear completed history only after the target result is understood.
Troubleshooting
- The same request returns after canceling: change or disable the original target or Bank support policy.
- Partially sent never finishes: review multiple-batch permission, remaining resources, ships, slots, and reserves.
- Arrival passed but status remains sent: check the live movement and allow another normal Bank check.
- Resources arrived but the upgrade waits: inspect the dependent feature’s queue, target, and prerequisites.
- Clear completed changes nothing: only finished history is removed; active requests remain.
FAQ
Can one request include several reasons?
Yes. Compatible building or research needs for the same destination can be represented together.
Does cancel recall a sent fleet?
No. It stops remaining request work but does not reverse a transfer already submitted.
What does in transit mean?
Those resources are already assigned to an outgoing Bank flight and have not yet been delivered.
Why do ships remain unavailable after arrival?
Cargo ships still need to complete their return flight to the Bank source.
Does targets complete mean construction or research finished?
It means the Bank requirement is no longer needed; the dependent feature has its own final status.
FAQ
What is OGameX Bank Transfer Queue?
A request is created for a building or research requirement when Bank support for that category is enabled. Several reasons for the same destination can be grouped into one request. The request then moves through waiting, sending, arrival, and completion states.