Troubleshooting

When something goes wrong, Grindstone tells you in an error message, and it records what happened in a log file on your computer. This topic covers both, and how to get what you find to Epiforge.

Error messages

When Grindstone can’t do something you asked, such as opening a workspace, importing a file or saving a change, it shows a message with a red title that names what failed, like Opening Workspace Failed or Unable to Import Folio, and a sentence saying why.

The message has two buttons:

• Copy puts the title and the whole message on your clipboard, so you can paste it into a message to Epiforge exactly as Grindstone wrote it.
• OK closes the message.

When a workspace stops saving

If Grindstone can no longer save changes to a workspace, it says so in a message titled Workspace Stopped Saving and closes the workspace. The last change you made wasn’t saved. Open the workspace again to see everything that was. If it keeps happening, copy the message and speak with a specialist.

Something unexpected

If something goes wrong that Grindstone didn’t anticipate, it shows a notice at the bottom of its window saying that something unexpected just happened, that it might be a good idea to quit and restart Grindstone soon, and that it wrote information to its log file. The notice stays until you close it.

The notice offers Send a Report…, which opens a report to Epiforge with the technical details of what happened already in it. You can read and change all of it before you send it, and nothing is sent unless you do. See Privacy for what a report includes and what’s taken out of it.

If Grindstone crashes and closes, it offers to send a report the next time it starts.

Quit and restart Grindstone when you can. If the notice comes back, the log file holds what Epiforge needs to find the cause.

The log file

Grindstone writes a log as it runs: what it did, and the details of anything that went wrong. It starts a new log file each month, named for the year and month, such as Log202611.txt for November 2026.

On Windows, the beta’s log files are in this folder:

%LOCALAPPDATA%\Packages\com.epiforge.tachyon.client_27xcxqx0sss1r\LocalState

To open it, press Windows+R, paste the folder’s path and press Enter.

On a Mac, the beta’s log files are in this folder:

~/Library/Containers/com.epiforge.tachyon.client.beta/Data/Library/com.epiforge.tachyon.client

To open it, in the Finder choose Go > Go to Folder, paste the folder’s path and press Return.

Getting help

The quickest way to report a problem is from Grindstone itself: Send a Report… on its notice when something unexpected happens, the report it offers after a crash, or a bug report from Help in Grindstone. Each one already carries the details Epiforge needs about Grindstone and your computer, and you see everything before it’s sent.

You can also speak with a specialist on this site. Say what you were doing when it happened, and include what Grindstone told you:

• For an error message, use Copy and paste it into your message.
• For anything else, open the log file for the month it happened, find the lines from that time (each line starts with its date and time), and paste them into your message.

Read what you paste first. A log can mention things from your workspaces, such as the names of views and statuses, and you decide what to send. The form takes messages of up to 10,000 characters and doesn’t take attachments, so send the part around the time of the problem rather than the whole file.