Troubleshooting

Local AI Is Not Ready

Open AI & Models and check that RenameClick Local AI is installed and ready. The initial download needs internet and available disk space. If a download failed, retry after checking the connection and storage.

If the model is installed but cannot start, check available RAM/VRAM and return advanced settings to a smaller context. Other applications also use memory. CPU fallback and model loading can take different amounts of time on different hardware; there is no universal startup time.

LM Studio Setup

To use LM Studio as an alternative provider, follow the step-by-step LM Studio setup with screenshots. It covers downloading a vision model, loading it, starting the server, and connecting RenameClick.

Audio Is Unavailable or Has No Useful Speech

Install Audio Transcription as well as a naming provider. With Local AI selected, RenameClick Local AI must also be installed. Check that the format is MP3, WAV, FLAC, M4A, or AAC and that the recording contains intelligible speech.

Silence, music, background noise, or a decoding error can prevent a useful result. For a long recording with the wrong topic, increase Analyze up to and retry. Sampling can still miss a short important passage.

Files Are Missing from a Batch

Check the file-type filter, supported extension, Recursive setting, and Batch File Limit. Folder drops include only direct files by default. Cloud-synced placeholders need their contents available locally.

RenameClick does not unpack archives or process every Office format. See the complete format list.

A Name Is Wrong or Too General

Compare the suggestion with the file. Text may be trimmed, a scanned PDF may have the relevant field after page one, or the model may misread the available content. Edit a single result or revise the instruction and retry related files.

With a custom prompt selected, put the language and format in the prompt. Ordinary Format and Output Language are disabled. More prompt text or a larger context does not guarantee improved accuracy.

Apply Fails

Check the error for permissions, an unavailable source/destination, or a file that another program moved or locked. Close an application holding the file if appropriate, restore access, and retry selected failures. Failed changes do not use apply credits.

If credits are exhausted, wait for renewal or upgrade. Credits and plans.

Search Cannot Start or Finds Nothing

Stop Rename processing and stop watching in all Auto Flow rules. With Instant Search installed, index the folder first: Index folder appears instead of Search until the first run finishes, and Update index when the folder changed since the last visit. Check the chosen folder, Recursive, file filter, and Batch File Limit. Describe the main document purpose or image subject rather than a detail that may be absent from the analyzed context.

Inspect Errors separately from files that did not match. AI Search.

Auto Flow Does Not Pick Up a File

Keep RenameClick running and check that the rule is watching, the source is available, and the file matches all filters. Name filters are case-sensitive. Use Preview matching files to check a sample and see why files are skipped. Empty files are skipped until they have content.

For cloud files, Loading file means Auto Flow is reading the contents and may be waiting for the sync application to download them. Processing includes the stability check that follows the read. Changes restart the readiness check. The default 0.5-second stability delay is not a download timeout. Readiness and retry timing.

If the rule shows Waiting for OneDrive files, or the name of your provider, start or restart the sync app and check your connection, then click Try again. For iCloud Drive, check that it is turned on in iCloud settings. Cloud storage in Auto Flow.

For a chain, confirm the earlier stage was applied and the output reached the next source. Check that the next rule is watching and includes subfolders if needed. Cycles and the same source with overlapping file-type filters are rejected.

In same-folder Match Folders, unmatched files remain in place and appear as errors. This is different from a separate destination’s output-root fallback. A rule whose destination is its source never processes a file it already renamed or moved; undo the record while watching is stopped to process it again. Auto Flow.

A Duplicate Changed Before Apply

The message The duplicate or its remaining copy has changed. Check the files and try again means the earlier duplicate check no longer matches the files. Cloud downloads can change a file’s size or timestamps after the initial check. Cleanup stops for that file rather than relying on the old result.

Move duplicate to Trash in Not applied still describes the proposed action; it does not mean the file was deleted. Stop watching and click Re-run to check the current contents of both files, including a remaining copy already moved to the destination. Review the refreshed result, then Apply. Re-run itself does not send a file to Trash or use apply credits. If the files are no longer duplicates, the rule processes the file normally instead.

If a later Apply succeeds, its current checks passed. The earlier failure describes the files at that earlier attempt, not a permanent ban on applying the operation.

A Preview Does Not Load

If the file is in a cloud folder and is not available on this computer, the preview says so. Click Open OneDrive, or the button with the name of your provider, make the file available, then click Retry with OneDrive. If the original was moved or deleted, a new preview cannot be created.

Undo Is Unavailable

In Auto Flow, click Stop watching first. Undo and Redo history is saved across restarts, but starting watching clears recent-action history. Eligible saved Applied records can still be selected for Undo after stopping. Clearing a record or removing its rule removes its app recovery information; applying a new action clears Redo. The separate Rename workspace keeps up to 10 entries in memory and loses that history on restart.

Copy undo requires an unchanged copy and an available original. For Moved to Trash records created in 2.16.1 or later, the unchanged file must still be in Trash and its original path must be free. If that path is occupied, move or rename the conflicting file before retrying; Undo will not overwrite it. Older cleanup records must be restored through the operating system’s Trash or Recycle Bin. Files removed from Trash cannot be recovered by app Undo. Auto Flow undo.

License Activation or Restore Fails

Connect to the internet and check the installation channel. Direct macOS and Windows use the license key and purchase email; the Mac App Store uses Apple purchase restoration. The purchases are separate.

Use Find My License for a direct purchase or contact support if an activation limit needs attention. Do not post a license key in a public issue.

Import or Context Menu Problems

Stop watching in all Auto Flow rules before importing settings. Check that the file is a RenameClick .rclick export. Import replaces supported settings and reloads the app; reconnect local paths and credentials afterward.

For a missing right-click action, launch the installed app and follow context menu troubleshooting.

Contact Support

Use the website support form or email support@pithly.app. Include the RenameClick version, operating system, installation channel, exact error, and the steps that led to it. For model startup issues, include CPU, GPU, and RAM details.