Error Code Reference

Contents

Error Code Reference#

Reviewing and Resolving Errors#

This topic covers how to resolve error messages you may encounter as you use Rebus. The following errors can appear on a number of different screens, including while building widgets, using the Associate Portal, and while using Dashboards.

Rebus Errors#
Error	What the Problem is…	What You Need to Do…
CSV is either missing data or contains superfluous and/or incorrect fields.	Occurs when the system tries to import a CSV file into a custom table but cannot match the column headers or data types properly.	Double-check your column headers. They must exactly match the system’s expected field names, including capitalization and blank spaces.
PlanExecutor error during aggregation :: caused by :: cant $divide by zero	This error occurs during widget building when the system tries to divide a number by zero. For example: fields are calculated by dividing values (like DOWNTIME or MEASURED) by TOTAL_TIME. But if TOTAL_TIME is ever zero, the division fails.	Use a condition to only divide when the divisor is greater than zero:Percent_of_X = condition(greaterThan(TOTAL_TIME, 0), divide(VALUE, TOTAL_TIME), 0)
PlanExecutor error during aggregation :: caused by :: $substrCP: starting index must be a numeric type (is BSON type null)	This error occurs in widget building because you’re trying to take a substring of a value, but the starting position is null. If a string field is null, then functions like stringLength() or subtract() also return null.	Check that all fields used in calculations are clean, numeric, and consistently formatted.
Error loading the widget data: Bad Request, PlanExecutor error during aggregation :: caused by :: Failed to parse number ‘___’ in $convert with no onError value: Did not consume whole string.	Occurs during widget building when the system is trying to aggregate values across a dataset (e.g., summing, averaging, comparing), but one or more fields expected to be numeric contain non-numeric data.	Use isNull(field, default) before doing math or substring operations.
Error Saving Widget Changes	Potentially corrupt widget.	Contact the implementation team.
Error Saving Copied Widget	Potentially corrupt widget.	Contact the implementation team.
Error Saving Modified Widget	Potentially corrupt widget.	Contact the implementation team.
Failed to publish dashboard. Reason: ReferenceError: err is not defined	Potentially corrupt dashboard.	Contact the implementation team.
Error loading the widget data: Widget or Super widget has inactive query	A widget within your combined widget may have been deactivated.	Check your inactive widgets and ensure none of the widgets that are part of the combined widget have been deactivated.
User not found (in Associate Portal)	Potential network connectivity issue or misspelling.	Check network connectivity & spelling of username.
Application Error at location: CgwBCwkCAQs User account does not exist	New user sign in- likely due to a spelling error or mistake in setting up the new user.	Check spelling in email and/or username. If correct, check with whoever set up the user and confirm that there were no spelling errors in setup.
Activity is still in progress (in Associate Portal)	An activity is still in progress that is preventing you from performing another action.	Make sure that you stop any ongoing activities before performing your action.

Reviewing and Resolving Error Transactions#

This topic covers how to resolve transactions that weren’t successfully migrated from the WMS to Rebus.

Note

There is a Save Grid State button on the Transaction Error Review page that allows you to save any changes made to your grid when you reset or make other changes in the fields section.

Resolving Quarantined Transactions#

Quarantined Transaction Errors#
Error	What the Problem is…	What You Need to Do…
Null Activity ID	Activity ID field is not populated in the incoming data.	Check to see that the activity groups are properly configured. If you can’t find the configuration issue or you otherwise can’t resolve it, contact Rebus Customer Support.
Null ActivityId – More than one row matched for the <attribute matrix name> Matrix for AUX value	Transaction has a value in the mapped auxiliary field that matches more than one row in the mapped attribute matrix, because the attribute mapping expression uses the LIKE or NOT LIKE operator.	Either correct the mapping attribute expression of the activity group by selecting the right operator. or correct the matrix by including only one row with the right lookup value.
Null ActivityId – Cannot perform mathematical operator(>) on String data field<(field name)>	Mapping attribute expression uses a mathematical operator (>, >=, <, <=), and the transaction’s AUX value format is a string.	Either correct mapping attribute expression of the activity group by selecting the right operator, or correct the matrix by changing the vector value.
Invalid User	This transaction’s user is not set up as a labor user.	From the Transaction Error Review screen, set up the transaction’s user as a labor user. For more information on how to set up the labor user, see Creating a Labor User from the Transaction Error Review Screen.
Invalid Activity ID	Activity ID field is populated with an invalid value in the incoming data.	Set up an activity type for this transaction. For more information about how to set up activity types, see Setup Procedure 6 of 7: Setting up Activity Types for Imported Transactions.
Invalid Activity Group	Activity group field is populated with an invalid value in the incoming data.	Set up an activity group for this transaction. For more information about how to set up activity groups, see Setup Procedure 5 of 7: Setting up Activity Groups.
Invalid QTY	Invalid quantity value in the incoming data. Quantity cannot be null or less than or equal to zero.	Contact Rebus Customer Support.
Invalid Step	Steps in the incoming transaction don’t match the step configuration in the activity type. E.g., Activity type is configured to have one step called START, but incoming transaction has STOP as step value. A labor user probably isn’t correctly following your processes.	Make sure that the labor user understands how to properly follow your processes. If this is a transaction that you don’t need to preserve, you can delete the transaction. For more information, see Deleting Transactions. Otherwise, contact Rebus Customer Support.
Extra Indirect Signoff	The non-essential transaction has an extra stop step. Non-essential transactions should have one Start and one Stop step. An extra Stop step can happen when a user in the WMS stops the transaction multiple times by mistake.	Caused by a user forgetting to stop a non-essential transaction, starting another transaction, and then remembering later on to stop the non-essential transaction, which results in an extra stop step. Make sure that the labor user understands how to properly follow your processes. If this is a transaction that you don’t need to preserve, you can delete the transaction. For more information, see Deleting Transactions. Otherwise, contact Rebus Customer Support.
Query UOM does not match configured UOM	The labor transaction’s UOM in your WMS doesn’t match the configured activity type’s UOM in Rebus.	If the configured UOM in Rebus is incorrect, change it to the correct UOM, and save the activity type. To find out where to change the UOM, see Setup Procedure 6 of 7: Setting up Activity Types for Imported Transactions. Otherwise, please contact Rebus Customer Support.
Invalid Modification	Rebus cannot find the SIGN-ON or SIGN-OFF to be updated or deleted.	Confirm that the user’s last SIGN-ON or SIGN-OFF is correct from the Activity Adjustment Admin screen. If it’s correct, delete the quarantined transaction. If it’s incorrect, contact contact Rebus Customer Support.
Invalid Time Component # - <Time component name> - Combination not found in <Matrix name>	Transaction does not satisfy time component mapping.	Compare transaction’s auxiliary fields to time component mapping - all fields that are included in the mapping must be populated for the transaction.
Invalid Time Component # – <Time component name> – More than one row matched for the <Matrix name> matrix	Transaction has a value in the mapped auxiliary field that matches more than one row in the mapped numeric matrix, because the time component expression uses the LIKE or NOT LIKE operator.	Either correct the time component expression of the activity type by selecting the right operator, or correct the matrix by including only one row with the right lookup value.
Invalid Time Component # – <Time component name> – Cannot perform mathematical operator(>) on String data field <(field name)>	Time component expression uses a mathematical operator (>, >=, <, <=), and the transaction’s AUX value format is a string.	Either correct the time component expression of the activity type by selecting the right operator, or correct the matrix by changing the vector value.
Invalid Time Component # – <Time component name>	Configured time components or mapping atributes are missing information. The root cause could be any of the following:
	Possible Root Cause 1: Transaction has a value in the mapped auxiliary field that cannot be found in the corresponding vector of an attribute matrix.	Add missing value (e.g., location) to the attribute matrix, with the corresponding value to be returned.
	Possible Root Cause 2: Transaction has a value in the mapped auxiliary field that cannot be found in the corresponding vector of a vector matrix	Add missing value (e.g., to & from zone combination) to the numeric matrix, with the corresponding value to be returned.