Revit Add-ons: Free Ze’Diag: Revit Journal Analyzer

Overview

Ze’Diag is a free diagnostic tool from ZestineTech that explains why Revit crashed or misbehaved. Revit records every action, add-in call, and error in a session in a plain-text journal file. These files run to thousands of lines and are hard to read by hand. With Ze’Diag, you upload a journal and get back a structured, readable report. The report covers whether Revit crashed, the likely root cause, the errors and warnings raised, links that failed to load, where time was lost, and which add-ins may have been involved. It also links to known Autodesk solutions where they apply. The report can be downloaded as a PDF to share with the team. ZestineTech's pitch is to diagnose crashes "in minutes, not hours."

Note on sources and scope: Ze’Diag isn’t installed inside Revit. It’s a web application you open in a browser, and it’s listed on the Autodesk App Store as a "web-based Autodesk Revit journal analyzer." Some directories group it under Revit add-ins and scripts because it’s part of the Revit tool ecosystem. This summary is based on ZestineTech’s product page, the Ze’Diag web app’s own pages, the Autodesk App Store listing, ZestineTech’s LinkedIn posts, a third-party directory entry, and Autodesk’s documentation on journal files. I found no independent reviews or hands-on tests. Performance claims, such as the speed of the analysis and the crash statistics on the product page, come from ZestineTech.

The Problem It Addresses: Reading Revit Journals

Autodesk's documentation explains what journals are and why they matter, and it shows why a tool like Ze’Diag has a place:

Revit writes a journal every session: A new journal file (for example Journal.0001.txt) is created each time Revit starts, and the highest number is the most recent. Journals record activity from startup to shutdown. They're normally stored under the user's local AppData folder, in Autodesk\Revit\Autodesk Revit [version]\Journals, which is hidden by default in Windows.
They hold the answers but are hard to read: Autodesk describes journals as useful for troubleshooting both on the affected machine and remotely. Reading them takes practice, because you have to know what to search for, such as exceptions, fatal errors, add-in entries, and the last successful command before a failure. ZestineTech notes that most BIM users aren't trained to do this.
Other files travel with them: The journals folder can also hold dump files (.dmp) created when the program crashes, plus worker logs and abbreviated journals. Autodesk tells users to send a dump file to Product Support along with the journal.
Crash investigations are manual: Common practice is to open the journal in a text editor, search for keywords, find the last successful command and the first error, and isolate suspect add-ins. Autodesk also offers a Notepad++-based search method for documented issues.

Ze’Diag automates that first-pass reading and presents the result in a consistent report format.

Key Facts

Type: A cloud-based web application, with nothing to install. A directory entry lists the deployment as cloud/SaaS.
Input: A Revit journal file (.txt), uploaded by drag and drop or browsing. The web app has a "Copy Path" button to help you find where your journals are.
Where to get it: ZestineTech's product page (zestinetech.com/zediag), the web app (zediag.zestinetech.com), and the Autodesk App Store.
Large files: A directory entry says content in the middle of a journal larger than 100 MB is truncated. I couldn't confirm this on ZestineTech's own pages.

How It Works

Find your journal: Locate the journal for the session that crashed or misbehaved. The newest file is the most recent session. The web app shows the folder path so you can copy it.
Upload it: Drag the file into the page or browse for it, then choose Analyze Journal. You'll be asked to log in or create an account at this point.
Read the diagnosis: The journal is parsed in seconds into a structured report, which you can review on screen and download as a PDF.

ZestineTech's own examples show the kind of journal events it reads, such as a document sync starting, a transaction beginning, a regeneration, and a geometry warning followed by an unhandled exception. The tool is meant to be used after a crash, a freeze, or odd behavior in Revit, once the journal exists.

What the Report Contains

The web app presents four main capabilities, organized into report tabs that include Session Info, Revit Crash Report, Issues & Errors, Timeline, Add-ins, Workflow, KB Articles, Unsaved Work, and Actions:

Crash Analysis: The likely reasons behind a crash, taken from the session events. The crash report is laid out as a root cause, fatal errors detected, an explanation, an immediate action required, and forensic evidence. If the session ended normally, the report says no crash was detected.
Errors and Warnings: Every problem found, with recommended solutions. Known issues spotted in the journal are linked to official Autodesk solutions through the KB Articles tab.
Session Timeline: What happened in the session, step by step, including synchronization operations, files, and links. It highlights significant delays, defined as more than 5 seconds between consecutive events, so you can see where time was lost.
System Overview: The hardware, Revit build, and add-ins in use at a glance. The Add-ins tab helps point to add-ins that may have been involved.
Missing links: Linked files that were referenced but couldn't be found, with a pointer to resolve them through Manage > Manage Links in Revit.
Unsaved work: A dedicated tab on unsaved work, which suggests it helps judge what may have been lost. I couldn't find a description of how it works.
PDF report: A detailed downloadable report so teams can review issues, collaborate on fixes, and keep project documentation.

Compared with Reading a Journal by Hand

Task	Manual journal reading	Ze’Diag
Find the crash and its cause	Search a text editor for exceptions and fatal errors, then work backward from the last good command	Root cause, fatal errors, explanation, and evidence in a structured report
Spot add-in involvement	Check which add-ins loaded and ran before the failure, and test by disabling them	An Add-ins view that points to add-ins that may have been involved
Find documented fixes	Search Autodesk's knowledge base, or use a Notepad++ search file	KB Articles linked to issues detected in the journal
See where time was lost	Compare timestamps by eye	Timeline that flags delays of more than 5 seconds
Find missing links	Search for failed link loads	A list of missing linked files, with the Manage Links path to fix them
Share findings	Paste excerpts or send the raw file	A downloadable PDF report
Handle dump files (.dmp)	Send to Autodesk Product Support with the journal	Not mentioned; the tool reads journal files

Privacy and Handling Journals

What the vendor says: The web app states that your journal is "analyzed briefly and never stored." It also says it uses cookies and privacy-respecting analytics to understand usage, with a Privacy Policy link and an option to decline.
Why it matters: Revit journals can contain file paths, user names, machine names, and network share names. Revit community guidance advises treating them as sensitive and redacting details before sharing them. If your firm has data-handling rules, check them before uploading journals from client projects, and review ZestineTech's Privacy Policy.
Account required: Analysis needs a login or a new account, so some user information is shared with ZestineTech. I didn't find details on what is collected.

Fit for a BIM Coordinator

Where it helps: Triaging crashes quickly across a team, checking whether the same add-in or link keeps appearing, and giving help-desk staff and BIM managers a consistent report. It also fits add-in vetting, since the report shows which add-ins were loaded during a failed session.
Before escalating to Autodesk: It's a quick first pass before you send journals and dump files to Autodesk Product Support. It doesn't replace the support process, because support will still want the original files.
Where to be careful: The analysis explains likely causes, so treat it as a lead to verify, not a final verdict. Test the suggested cause, for example by disabling an add-in or unloading a link, before changing standards or blaming a tool.
Pairing with other tools: It complements model-health tools. Those check the model's contents, while Ze’Diag looks at what happened in a session.

Open Questions

How accurate is the root-cause analysis, and what does it do when a journal is ambiguous? There's no independent testing.
How are large journals handled? A directory entry mentions truncation above 100 MB, but ZestineTech's own pages don't confirm it.
What does the Unsaved Work tab show, and how reliable is it?
What data does the account sign-up collect, and what do the Privacy Policy and End User Agreement say about uploaded journals?

Bottom Line

Ze’Diag is a free, browser-based tool that turns a Revit journal file into a readable diagnostic report. The report covers the likely cause of a crash, the errors and warnings raised, the add-ins involved, missing links, a session timeline, and linked Autodesk fixes, and it can be downloaded as a PDF. It isn't a Revit add-in you install, but it fits naturally into a BIM coordinator's troubleshooting routine. It speeds up first-pass triage and makes crash reports easier to share. Its main limits are the lack of independent testing, the need to create an account, and a privacy question, because journals can contain file paths and user names. A sensible first step is to run it on a few recent journals from your own sessions, compare the results with what you already know about those crashes, and review ZestineTech's privacy terms before using it on client-project journals.

Sources