Please visit our new TrackAbout Knowledge Base at https://supportkb.trackabout.com for the most-up-to-date documentation on TrackAbout and TrackAbout Mobile.
Difference between revisions of "Collision Resolution Error"
(Created page with "==Collisions - Link to review== To review what collisions are and how to resolve them please go here: Collisions ==What happens when a Collision Resolution Error happen?...") |
|||
| Line 14: | Line 14: | ||
There are two issues that make up the vast majority of collision resolution errors and they are based on two of the golden rules of the TrackAbout asset tracking system. A customer's balance cannot fall below zero, unless another configuration permits it (see [[Exchange Balances]]) and two different records cannot have the exact same effective date/time. | There are two issues that make up the vast majority of collision resolution errors and they are based on two of the golden rules of the TrackAbout asset tracking system. A customer's balance cannot fall below zero, unless another configuration permits it (see [[Exchange Balances]]) and two different records cannot have the exact same effective date/time. | ||
| − | ===Potential Negative NS balance=== | + | ===Potential Negative Not Scanned (NS) balance=== |
These errors occur when the resolution of a collision would reduce a balance to below zero. Because TrackAbout does not allow a customer balance to fall below zero, an error is generated. | These errors occur when the resolution of a collision would reduce a balance to below zero. Because TrackAbout does not allow a customer balance to fall below zero, an error is generated. | ||
Generally the underlying cause will be a Reduce NS balance, Customer Audit, or RightSize action that has been performed on a customer account. | Generally the underlying cause will be a Reduce NS balance, Customer Audit, or RightSize action that has been performed on a customer account. | ||
Revision as of 16:09, 26 March 2015
Collisions - Link to review
To review what collisions are and how to resolve them please go here:
What happens when a Collision Resolution Error happen?
The work flow for these issues follow this flow: An error is generated in TrackAbout and emailed to the Support Team as a ticket Once the ticket is in the support queue it will be addressed as quickly as possible After the problem has been resolved, a TrackAbout Support Specialist will email the customer that attempted to resolve the collision. There are times that our attempts to resolve the underlying problem did not resolve the issue or that it uncovered another issue with that collision resolution. If that happens then when that collision is attempted again, a new error will be generated and sent to TrackAbout.
The Underlying Cause
There are two issues that make up the vast majority of collision resolution errors and they are based on two of the golden rules of the TrackAbout asset tracking system. A customer's balance cannot fall below zero, unless another configuration permits it (see Exchange Balances) and two different records cannot have the exact same effective date/time.
Potential Negative Not Scanned (NS) balance
These errors occur when the resolution of a collision would reduce a balance to below zero. Because TrackAbout does not allow a customer balance to fall below zero, an error is generated. Generally the underlying cause will be a Reduce NS balance, Customer Audit, or RightSize action that has been performed on a customer account.
- An action that would return an asset causes a collision - This collision is not resolved promptly. If it were resolved at this point, no collision resolution error would occur.
- The customer balance is modified through a bulk action, such as a Customer Audit.
- An attempt to resolve the collision from step 1 now generates an error because it is attempted to reduce the customer balance and that balance was already reduce via an Audit (or similar action)