Troubleshooting

Every message WarrantySync shows comes from one place. This guide lists them all, says where you would see each one, and says what to do about it.

If you are looking for how a screen works rather than why it is complaining, start at the guide index.

How to read an error

WarrantySync states a problem in two parts. The title names the thing that failed. The message names the fix. Both come from a single taxonomy in the code, so the same failure reads the same way wherever it appears — a banner on the dashboard, a message under a settings field, or a line on a warranty card.

Three consequences are worth knowing:

• No message ever contains a key, a token, a stack trace or a raw reply from a manufacturer. If you need that detail to diagnose something, it is in forge logs, not on screen.
• A message that promises a retry means the app will retry by itself. A message that names a field or a setting means it is waiting for you.
• Something went wrong is reserved for causes the app genuinely could not identify. If you see it for something you can obviously fix, that is a defect worth reporting.

Every message, and what to do

Code	Title	Message	Where you see it	What to do
auth_vendor	The manufacturer rejected the credentials	Names the manufacturer, then: rejected the credentials. Check them on the WarrantySync settings page.	Settings, on a credential card after Test connection; dashboard, after a run	Re-enter that manufacturer’s credentials and test again
auth_jira	Jira refused the request	Jira rejected a request the app needs to make. Check that the app still has permission to read devices and create issues.	Dashboard, when a non-administrator presses a run control, or when the app’s own permissions have been changed	Check you are a Jira administrator; check the app is still installed with its scopes
rate_limited	The manufacturer is rate limiting us	Rate limited. The app backed off and will pick up where it left off.	Dashboard, during or after a run	Nothing. The app resumes by itself
no_warranty_found	No warranty found	The manufacturer returned no warranty for this serial number.	Issue panel, on a device card	Check the serial is the manufacturer’s own service tag, not an asset label
missing_serial	No serial number	This device has no serial number, so it cannot be looked up.	Issue panel; the pre-scan buckets	Fill in the serial field on the device record
unsupported_vendor	Manufacturer not supported	Warranty lookup covers Dell, Lenovo and HP.	Issue panel; the pre-scan buckets	Nothing to fix. The device is counted but never looked up
mapping_missing	Field mapping incomplete	WarrantySync does not know which field holds the serial number or the warranty end date. Set the mapping on the settings page.	Dashboard, before setup is finished	Finish the Device source tab on the settings page
source_unavailable	Device source unavailable	WarrantySync could not reach the device source. Check the source and mapping on the settings page.	Dashboard	Check the project or object schema still exists and the app can still read it
dedupe_uncertain	Could not confirm an existing issue	The app could not confirm whether an expiry issue already exists, so it did not create one.	Dashboard, after a run	Nothing. Not raising a duplicate is the intended outcome
capacity	Storage limit reached	WarrantySync has reached its per-site storage limit. Warranty data is still being written to your devices, but the dashboard list has stopped growing.	Dashboard	Warranty write-back still works. The device list will not grow further
validation	That value cannot be saved	Check the value you entered and try again.	Settings, under the field that was rejected	Correct the value the page has marked
busy	WarrantySync cannot start a run yet	WarrantySync cannot start another run yet. Try again shortly.	Dashboard, when a run is already going or the manual cooldown is active	Wait. The dashboard says how long
unknown	Something went wrong	Something went wrong. The next scheduled run will retry.	Anywhere	Retry once. If it persists, report it

The capacity row is the one message in this table that has not been photographed for these guides. Reaching it needs an estate of more than ten thousand devices, which the documentation site does not have. The wording above is quoted from the code rather than from a screenshot.