NameSenseFind the step that failed
Keep the current files and note the exact message before retrying. Start with one practice copy. A successful import, preview and rename are three different results.
Scroll sideways to see the full comparison →
| What you see | Check first | Next action |
|---|---|---|
| No file in the list | Is it an extracted, supported file that opens normally? | Use one practice file and follow the import checks below. |
| Generation fails | Does the same file work with Add Date? Does the AI rule report a service error? | Separate local file access from AI requests; continue to AI setup for connection and model errors. |
| Preview exists; Finder is unchanged | Did you only generate suggestions, or also apply Rename? | Review the selection and apply it, then verify the actual result in Finder. |
| Rename or undo partly fails | Is a name occupied, a file missing, or folder access needed? | Keep the current files. Read the item errors and follow the conflict or undo steps below. |
A file will not import or generate a suggestion
First separate a file-access problem from an AI request problem. Buying Pro or changing the API key will not repair a damaged file.
- Open the file in Finder with its usual app. Check its extension against the supported-format list. Extract ZIP samples first and select the files inside; whole folders and ZIP archives are not supported inputs.
- Try one readable .txt practice file with the built-in Add Date rule. Check that it appears in the list and can generate a suggestion. This local rule needs no AI service; use the getting-started exercise if you need a sample.
- If Add Date works but an AI rule fails, open the AI troubleshooting guide. If only one document fails, check whether it is encrypted, damaged or beyond extraction limits. Report the file type and exact error if even a readable practice file will not import.
Suggestions appear, but filenames have not changed
Generate Names creates a preview. It does not change the filenames in Finder. Apply the reviewed changes as a separate action.
- Compare the original and suggested names, including the extension. Select the intended files and resolve any visible warning before continuing. The Rename button shows how many selected files will be processed.
- Click Rename for that selection. If NameSense asks for folder access, select the folder containing those files as prompted. If access is still denied, try a practice copy in a folder you can edit to check whether the original location is the problem.
- Wait for the result, then check the actual names in Finder. If only part of the batch completed, inspect the failed items and their errors. Do not assume every item changed or rerun already-renamed files without reviewing the next preview.
A name conflict blocks the rename
Two suggestions may be identical, or the destination folder may already contain a file with that name. Resolve the conflict before applying.
- Compare the conflicting suggestions with the files already in the destination folder. Check the full names and extensions, not just the visible title.
- Edit the suggestion or adjust the rule. A serial number or a meaningful prefix can distinguish files. Generate and review the new suggestions again; a changed rule does not make existing destination files disappear.
- Apply only after the warning is resolved. Keep the existing destination file. If you cannot explain the conflict, send the error and an anonymized before/after filename example to support.
Undo does not restore every filename
Undo needs access to the renamed files and a safe path back to their original names. Moving or renaming files in another app can prevent recovery.
- Read the undo result and compare it with Finder. Check whether each file still exists, whether an original name is occupied, and whether NameSense is requesting folder access.
- If the problem is missing folder access, follow the prompt to authorize the relevant folder, then retry the failed operation. Do not delete an occupied file or manually rename a whole batch to imitate an undo.
- If files moved, changed or only partly recovered, stop additional renames and note the current names and locations. Contact support with the app version, the error and which items actually changed. If no rename was applied, a generated preview alone creates nothing to undo.
A Direct purchase has not unlocked Pro
These steps apply to purchases made through NameSense Direct. Provider API credits are separate from Pro, so an AI balance error is not a failed Pro activation.
- Return to the same app installation that started the purchase and let it check the result. A payment page alone is not confirmation that the app has refreshed its entitlement.
- Open Settings → NameSense Pro and click Refresh Direct Purchase. Wait for the result and read any pending-verification or connection message before trying again.
- If it remains locked, copy the Purchase ID from that settings page and contact support with your order reference, app version and error. On a different Mac or after reinstalling, mention that too. Do not purchase again to fix the problem. Older email orders use their original recovery process; refund instructions depend on the purchase route.
Send a useful report or ask about your data
Use the copyable report template below. Include the failing step, file type and count, selected rule, expected result, actual result and exact error. For AI problems, add the provider and model, and say whether Test Connection succeeded.
- Use an anonymized filename example or a cropped screenshot when it explains the problem. Remove API keys, passwords, private file contents and payment details before sharing. A small non-sensitive reproduction is more useful than an entire folder.
- For purchase-identity or operator-held data deletion requests, contact support. Uninstalling the app may leave Keychain entries. For a security report, include Security in the email subject and describe only the necessary technical details.