Troubleshooting

The four things that come up, and what each of them usually is.

Nothing moves

Check the status row on Overview.

• An orange dot means macOS is blocking access — see First launch.
• A grey dot means filing is paused, or has not been started yet. The headline says which, and Start Filing… answers the second.

Worth ruling out too: filing only runs while the app is running, so if the Mac restarted and Tideline is not set to open at login, nothing has been sweeping.

Files are filed under the wrong day

The day comes from the date the file landed on disk, so something copied or restored from elsewhere carries the date of the copy. Switch Sort by to Date last modified on the Filing pane if that suits you better.

A file stayed put that should have moved

Anything written to in the last 30 seconds is left alone, on the assumption that something is still filling it in. The next sweep picks it up.

If it keeps staying put, check it against the skip list: hidden files, partial-download extensions, and anything matching a name or pattern under Never touch these are all held back deliberately.

“Unable to expand … It is in an unsupported format.”

You downloaded the build artifact from the Actions run page rather than an asset attached to the release. GitHub wraps every artifact in a zip of its own, so that download is a zip inside a zip — unpack it twice. Better, take the disk image from the latest release, which has nothing to unpack at all.

Still stuck

The full record, sweep by sweep, is at ~/Library/Logs/Tideline.log — General › Open Log File. Quote the version and build number from the foot of the General pane and open an issue.