Error messages
This page lists the messages the oneGRID app shows when something cannot be completed, grouped by the screen or process they appear on. Each entry gives the message as the app displays it, what it actually means, and what to do next.
Messages that contain a placeholder such as {0} are shown
with the concrete item, container, or location filled in. The German site shows
the German wording of each message; this page quotes the English one.
If you know the symptom but not the message, start from Troubleshooting instead. Messages that the oneGRID API returns rather than the app itself are listed under API result codes.
Picking
These messages appear on the Picker page and in the dialogs that open while you work through a work order.
| Message | What it means | What to do |
|---|---|---|
No work orders are currently available for processing. | No order matches the storage and filters you selected — or every order is already being processed by someone else. | Check the work order list and your storage selection; see Manage work orders. |
Selected storage does not have any items available to pick. | The storage holds no placements for the requested items, so no pick can be guided. | Place stock in the storage or select a different one; see Check and adjust stock. |
Active policy does not allow starting work orders which cannot be completed. | The storage is configured to refuse orders whose stock is insufficient to fulfil every position. | Replenish the missing stock, or ask an administrator to relax the policy in Storage settings. |
Currently selected process is not supported by preferred storage. | The process you picked is not enabled for the storage set as your preferred one. | Choose a different process or storage, or have the process enabled in Process configuration. |
Not enough stock | The recorded stock is smaller than the requested amount. | Confirm the reduced amount the dialog offers, or correct the stock first; see Check and adjust stock. |
There is not enough item stock for {0} to fulfill the request. | The detail behind Not enough stock: it names the item and offers the amount that is actually available. | Accept the offered amount to pick a partial position, or cancel and replenish the stock. |
Confirmed amount exceeds placed amount. | You confirmed more pieces than the location is recorded as holding. | Re-count and confirm the real amount; if the record is wrong, correct it in the inventory afterwards. |
The work order does not exist! | The order was deleted or its number was mistyped or misscanned. | Check the number and open the order from the list instead of typing it. |
Work order cannot be abandoned because it is placed on storage. | The order is still attached to a storage, so it cannot be taken out of processing. | Detach it from the storage first; see Cannot edit or abandon a work order. |
Work order is already completed. | Someone else finished the order, or you scanned a number that has already been closed. | Pick another order from the list; the closed one is visible under History. |
Work order is marked as abandoned and cannot be started. | The order was taken out of processing manually and is not available for picking. | Restore it from the History first; see Manage work orders. |
This work order cannot be edited because it is completed, abandoned or external. | Only open, internal orders can be changed. External orders are read-only by design. | See Cannot edit or abandon a work order and Work order statuses. |
Insufficient stock to fulfill the request. | The recorded stock cannot cover the position, reported from the processing step rather than the dialog. | Replenish the stock or confirm a partial pick; see Check and adjust stock. |
The work order is empty. | The order carries no positions, so there is nothing to pick or sort. | Check the order's source; an empty imported order usually means the external system sent no lines. |
Item {0} does not exist. Do you want to create it? | The scanned item number is unknown to oneGRID. The dialog offers to onboard it on the spot. | Confirm to create the item, or cancel and check the number; see Manage items. |
Picking progress is temporarily unavailable | The progress display lost its connection to the server. Picking itself continues to work. | Keep working; the display recovers on its own or after a page reload. |
Additional input will be required for confirmation because this location contains many containers and location scanning is selected confirmation option. | A notice, not a failure: because several containers sit on the location, a location scan alone cannot identify the withdrawal. | Expect an extra container scan at this step. |
Scanning a container while picking
When the storage requires container scanning, oneGRID checks the scanned container against the placement it expects. These messages explain why a scan was rejected.
| Message | What it means | What to do |
|---|---|---|
Container '{0}' was not found at the selected location. | The scanned container is not recorded at the location the light points to. | Check that you are at the signalled location and scanned the right container code. |
Container '{0}' does not contain the required item. | The container exists at the location, but holds a different item. | Scan the container that actually holds the requested item. |
Container '{0}' has no pickable amount of the required item. | The container holds the item, but the recorded amount is zero or already reserved. | Scan another container at the location, or correct the stock; see Check and adjust stock. |
All placements of the required item in container '{0}' have already been confirmed. | You already confirmed everything this container contributes to the current position. | Scan a different container, or submit what you have picked. |
Multiple containers at this location hold the requested item. Please scan the container you picked the items from to continue. | oneGRID cannot decide which container the stock left, so it needs the scan to book the withdrawal correctly. | Scan the container you actually picked from. |
Some of the requested item is in a container that cannot be scanned. Did you pick from a scannable container? | Part of the stock sits in a container without a scannable code, so the scan cannot account for the whole amount. | If you picked from the unscannable container, confirm without scanning; otherwise scan the container you used. |
Cart picking
These messages appear while setting up or running a PickCart process.
| Message | What it means | What to do |
|---|---|---|
You are not authorized to use the cart. | Your user is not permitted to work with the selected cart. | Ask an administrator for the cart permission; see Permissions and presets. |
Missing permission: {0} for all carts or for the selected cart. | The named permission is granted neither globally nor for this cart. | Have the permission assigned for the cart in question. |
Cart processing does not support placing requests. | The order contains a placing position, which cart picking cannot execute. | Process the order with a different method; see Place items and containers. |
No containers available in the cart to attach work orders. Add more containers or start processing the attached ones. | Every cart location is already taken by an attached order. | Finish or detach an attached order, or add containers to the cart. |
Attaching all work orders failed. | None of the selected orders could be attached to the cart. | Retry; if it persists, check the cart configuration and the orders' statuses. |
Attaching some of work orders failed. | Part of the selection was attached; the rest was rejected, usually because cart locations ran out or an order changed status. | Check which orders are attached and retry the remainder. |
Configuration is missing. To get started, click the Configure button below. | The cart has not been configured yet, so no process can start. | Configure the cart; see Cannot start cart picking. |
Cart with this name does not exist in the system anymore. | The saved configuration refers to a cart that has since been deleted. | Create the cart again, or configure the process against an existing cart. |
Failed to save configuration. | The configuration could not be written, typically a connection problem. | Retry; if it persists, contact technical support. |
Failed to clear configuration. | The existing configuration could not be removed. | Retry; if it persists, contact technical support. |
Could not load valid cart data. Please try to bind the cart again to this device or contact support for assistance. | The device is bound to a cart whose data cannot be read — usually the binding is stale after the cart was changed or deleted. | Bind the cart to the device again; see Cannot start cart picking. |
Put Wall and Manual Sorting
These messages appear while sorting items on the put wall or with Manual Sorting.
| Message | What it means | What to do |
|---|---|---|
The work order location could not be turned on. | The light for the order's location did not respond — usually an offline or unassigned device. | Continue by the location number and check the device; see Monitor devices. |
The work order location could not be turned off. | The light stayed on after the step was confirmed. The booking itself went through. | Check the device; the light clears on the next process start. |
Unable to start unloading together with placing for last item, falling back to placing last item. | The two steps could not be combined, so oneGRID performs only the placing step. This is a notice, not a failure. | Continue; unload the remaining containers as a separate step. |
Placing and inventory
These messages appear on the Place page and in the inventory views.
| Message | What it means | What to do |
|---|---|---|
The items could not be placed | The placing booking was rejected — commonly the location is full, blocked, or was changed while you worked. | Reload the page and retry; see Place items and containers. |
Location does not contain physical container | You are placing into a container, but the target location has no container on it. | Place a container on the location first; see Manage containers. |
Selected location does not exist. | The location was deleted or the scanned code does not belong to this storage. | Scan a location of the current storage, or check the rack configuration. |
An error occurred during searching inventory. | The inventory query failed; no stock data was returned. | Narrow the filter and retry; if it persists, contact technical support. |
Turning on light at location {0} failed. | The locate-light command did not reach the device. | Check the device state; see Monitor devices. |
Turning off light at location {0} failed. | The light stayed on after you switched it off. | Check the device; the light clears on the next process start. |
Onboarding a new item in this location will remove the existing one! This process cannot be undone. | A warning before a single-item location is overwritten: the item recorded there will be dropped. | Confirm only if the location really holds the new item; otherwise cancel and choose a free location. |
Location is already paired with code: {0}. | The location already carries a scannable code, and a location can hold only one. | Unpair the existing code before pairing a new one. |
The storage does not exist! | The storage was deleted or you no longer have access to it. | Reload the page and select a storage from the current list. |
Handling Location with many Placements not supported. | The chosen confirmation mode cannot handle a location that holds several placements at once. | Use a location with a single placement, or change the confirmation mode in Storage settings. |
This location is already reserved in the system for another item. | The location is configured for a different item, and single-item locations accept only their own. | Choose a free location, or clear the reservation first. |
Scanning and the camera
The oneGRID app can use the device camera as a scanner. These messages come from the browser, not from oneGRID.
| Message | What it means | What to do |
|---|---|---|
Camera API is not available in your browser. | The browser exposes no camera interface — typically an unsupported browser or a page served without HTTPS. | Open the app over HTTPS in a supported browser, or use a hardware scanner. |
Camera access has been denied. To reset the camera permission, please allow camera access in your browser settings. | The camera permission was refused for this site, either once or permanently. | Allow camera access for the site in the browser settings, then reload the page. |
Could not access the camera: | The camera could not be opened. The browser's own reason is appended after the colon. | Read the appended reason, then check the browser's camera permission for the site. |
Access and permissions
These messages appear instead of a page when your account, licence, or session does not allow the view. See Permissions and presets.
| Message | What it means | What to do |
|---|---|---|
Missing permission: {0}. | Your user lacks the named permission outright. | Ask an administrator to grant it; see Manage users. |
Missing permission: {0} for all storages or for the selected storage. | The permission exists, but not for the storage you selected. | Have the permission extended to that storage, or switch to one you are allowed to use. |
It seems that you currently do not have one of required features active to access this page. Get in touch with your IT or your organization to activate one of required features. | The page depends on a licence feature that is not enabled for your organization. | Contact your administrator; see A feature is not visible. |
Unable to fetch required session data. Please try to log out and then log in again, or contact support for assistance. | The session is incomplete or expired, so permissions cannot be evaluated. | Log out and back in; see Your account. |
Access to this view is temporarily unavailable, because we were unable to fetch required information about selected storage. Please try again later or contact support for assistance. | The storage data needed to decide access could not be loaded. This is a temporary fault, not a missing permission. | Retry after a moment; if it persists, contact technical support. |
It looks like you do not have permission to access this page. This may be because your account does not have the necessary permissions, or because the page is only accessible to certain users or groups. | The generic access-denied page, shown when no more specific permission message applies. | Ask an administrator which permission the page needs; see Permissions and presets. |
You do not have sufficient permissions to access this feature for selected storage. | You may use the feature in general, but not in the storage currently selected. | Switch to a storage you are allowed to use, or have the permission extended. |
We apologize, but it seems that you currently do not have an active license. Kindly get in touch with the IT department of your organization to activate your license. | Your account has no active licence at all, so the app cannot be used. | Contact your organization's IT department to activate the licence. |
Some options are unavailable due to your current license limitations. Please contact your IT department to enable these features. | The licence is active but does not cover every option shown, so some are greyed out. | Contact your IT department to extend the licence; see A feature is not visible. |
Storages, racks, and locations
These messages appear while configuring storages and racks or storage settings.
| Message | What it means | What to do |
|---|---|---|
Settings for storage could not be loaded. | The storage's own settings could not be read; the page falls back to defaults. | Reload the page before changing anything, so you do not save a default over a real value. |
Failed to load global settings. Experience may be degraded. | The site-wide settings could not be read, so features that depend on them may behave unexpectedly. | Reload the page; if it persists, contact technical support. |
This setting cannot be used because container tracking global setting is disabled. | The storage setting depends on container tracking, which is switched off globally. | Enable container tracking in General settings first. |
This storage already has {0} external locations configured. | The storage has reached its configured limit of external locations. | Remove locations that are no longer used before importing more. |
The rack does not exist! | The rack was deleted, or the link you followed is stale. | Reload the storage and open the rack from the current list. |
Shelf could not be retrieved! | The shelf data could not be loaded, so its locations cannot be shown. | Reload the rack; if it persists, contact technical support. |
This shelf does not have any location yet. | The shelf exists but has no locations configured, so nothing can be placed or picked there. | Add locations to the shelf; see Storages and racks. |
Unable to delete shelf. Please remove all configured locations within the shelf before attempting to delete | A shelf can only be deleted once it is empty of configured locations. | Delete the shelf's locations first, then delete the shelf. |
You must add ISAC devices first. | The action needs at least one ISAC device on the shelf. | Add the devices; see ISAC codes. |
You must add LED devices first. | The action needs at least one smartLED device on the shelf. | Add the devices; see Device setup. |
The segment for the rack guidance could not be turned on | The rack guidance light did not respond. | Check the device state; see Monitor devices. |
The segment for the rack guidance could not be turned off | The rack guidance light stayed on after it was switched off. | Check the device; the light clears on the next process start. |
The sensor confirmation button could not be turned off | The smartCAP button stayed active after the step was finished. | Check the device; see Monitor devices. |
Failed to import placements | The placement import did not run; no stock was changed. | Check the file against the expected format and retry; see Check and adjust stock. |
Problem occurred during loading of the storage. | The storage could not be loaded, so its racks and settings are unavailable. | Reload the page; if it persists, contact technical support. |
Problem occurred during loading of the rack. | The rack could not be loaded, so its shelves and locations cannot be edited. | Reload the page; if it persists, contact technical support. |
Failed locations update summary | The heading of the report listing which locations an import could not update, and why. | Work through the listed rows, correct them in the file, and import again. |
Duplicate storage | A storage with the same name already exists; storage names must be unique. | Choose a different name. |
Devices and presets
These messages appear while onboarding or monitoring devices, and on the device presets page.
| Message | What it means | What to do |
|---|---|---|
Device not found! | The device was deleted, or its identifier does not match any onboarded device. | Reload the device list and open the device from there. |
Connection to device cannot be established. Please try again later or contact support. | The controller did not answer — the device is offline, unpowered, or unreachable on the network. | Check power and network, then retry; see Monitor devices. |
This device cannot be deleted because it is in use by oneGRID system. | The device is still assigned to a rack, shelf, or process. | Remove the assignment first, then delete the device. |
Device is not yet assigned to any storage. | The device is onboarded but not yet placed in a storage, so it cannot guide anyone. | Assign it to a rack; see Storages and racks. |
Failed to turn on segment | A smartLED segment did not switch on. | Check the strip's power and connection; see Monitor devices. |
Failed to turn off segment | A smartLED segment did not switch off and may stay lit. | Check the device; the segment clears on the next process start. |
The segment could not be turned on | The same fault reported from the device detail page. | Check the strip's power and connection. |
The segment could not be turned off | The same fault reported from the device detail page. | Check the device; the segment clears on the next process start. |
Failed to turn off the sensors | The smartCAP sensors did not respond to the switch-off command. | Check the controller connection; see Monitor devices. |
Amount of SMCs to add must be greater than 0 and less than {0}. | The number of sensor units entered is outside the range the controller supports. | Enter a number within the stated range. |
This device preset is already in use. Deleting it will affect all related devices. | A warning before deleting a preset that devices still reference. | Reassign those devices to another preset first; see Device presets. |
Name is required | A name must be entered before the device or preset can be saved. | Enter a name and save again. |
Device could not been found! | The device detail page was opened for a device that no longer exists. | Return to the device list and open the device from there; see Monitor devices. |
Items and containers
These messages appear while managing items and managing containers, including bulk import.
| Message | What it means | What to do |
|---|---|---|
oneGRID system already has one item with the same number or external identifier. | The item number or external identifier is already taken; both must be unique. | Change the number or identifier, or edit the existing item instead. |
oneGRID system already has {0} items with the same number or external identifier. | The same clash, reported for a bulk import: the named number of rows duplicates existing items. | Remove the duplicate rows from the file and import again. |
The image is not valid! | The uploaded file is not a readable image, or exceeds the accepted size or format. | Upload a standard image file such as PNG or JPEG. |
Error occurred during getting items | The item list could not be loaded. | Reload the page; if it persists, contact technical support. |
oneGRID system already has one container with the same code. | Container codes must be unique across the system. | Use a different code, or edit the existing container. |
oneGRID system already has {0} containers with the same codes. | The same clash, reported for a bulk import. | Remove the duplicate rows from the file and import again. |
All containers already exist. | Every row in the import file matches a container that is already in the system; nothing was created. | No action needed unless you expected new containers — then check the codes in the file. |
Given container type: {0}, assigned to container: {1} does not exist. | The import references a container type that is not configured. | Create the container type first; see Location and container types. |
Given container: {0}, is already placed on location, and container type: {1} is too big for this location. | Changing the container's type would make it exceed the location it currently sits on. | Move the container off the location first, or choose a type that fits. |
Given container: {0}, is equivalent of an already existing one. | The row duplicates a container already in the system in every relevant field. | Drop the row from the import file. |
Fill required fields | One or more mandatory fields on the form are empty. | Complete the highlighted fields and save again. |
Fill required details | The same check, shown on the dialogs that collect container or location details. | Complete the highlighted fields and continue. |
Item not found! | The item was deleted, or the link or scanned number does not match any item. | Open the item from the item list; see Manage items. |
The import file contains duplicate entries. Please remove the duplicates and try again. | Two or more rows in the file describe the same item, so the import was rejected as a whole. | Remove the duplicate rows and import again. |
Duplicated numbers | The heading of the list naming which item numbers occur more than once in the import file. | Remove or correct the listed numbers. |
Duplicated external identifiers | The same, for external identifiers rather than item numbers. | Remove or correct the listed identifiers. |
Account, session, and data loading
These messages concern your own account and the data the app loads in the background. See Your account.
| Message | What it means | What to do |
|---|---|---|
Unable to fetch information about the user. | Your user profile could not be read, so the page cannot show account details. | Log out and back in; if it persists, contact technical support. |
Unable to load license details. | The licence information could not be read, so feature availability may be shown incompletely. | Reload the page; if it persists, contact technical support. |
Failed to load organization name. | The organization name could not be read. Nothing else is affected. | Reload the page. |
Loading data failed | A background data request failed; the view you opened may be empty or incomplete. | Reload the page; if it persists, contact technical support. |
Copying to clipboard failed | The browser refused the clipboard write, usually a permission or non-HTTPS issue. | Select the text and copy it manually, or open the app over HTTPS. |
Failed to export ISAC codes. | The ISAC code export did not produce a file. | Retry; see Export data. |
Your login session has expired. Please click below to reload. | You were signed in too long ago and the session timed out. | Click the reload button and sign in again. Unsaved input on the page is lost. |
We could not restore your session. It may have expired or cookies were cleared. Please click below to reload. | The session could not be resumed after a reconnect — commonly cleared cookies or a browser privacy setting. | Reload and sign in again; if it recurs on every reload, check that the browser accepts cookies for the site. |
Integrity error | The data submitted conflicts with what is already stored — typically a value that must be unique is not. | Check the fields the form highlights, especially identifiers, and save again. |