Troubleshooting

The most common things that go wrong, and what to do about them.

“Authentication failed” when opening logicreader.io

The live demo is gated by HTTP basic authentication. Your browser should pop up a username / password dialog the first time you visit. If you cancelled that dialog, fully close the browser tab and reopen the URL. If the credentials in your invitation no longer work, email us — we rotate them periodically and will send the latest pair.

XER file fails to import

• Wrong P6 version. We support XERs from P6 versions 7.0 onwards (released 2010). Older versions may parse but with missing attributes.
• Encrypted XER. If your IT have configured P6 to encrypt exports, the XER will look like binary garbage to LogicReader. Ask for an unencrypted export or use the CSV path instead.
• File over 200 MB. Some browser combinations choke on very large file uploads. Try Edge or Chrome on a desktop machine; Firefox on a laptop sometimes truncates.

CSV imports but rows are missing

Almost always one of:

• Two rows share the same (project_id, task_code). The second one silently overwrote the first. Use the XER if you can — it carries unique task_ids.
• A required column is missing or misspelled. Check against the column list in Importing from P6.
• Date strings in unexpected format. ISO-8601 (YYYY-MM-DD) is safest.

Layout looks scrambled / activities overlap

Click Re-layout in the toolbar. The first layout pass after a load can look untidy if the schedule has unusual cyclic-looking dependencies (rare, but it happens with badly maintained P6 files). A fresh layout pass usually settles it.

If activities still overlap after Re-layout, take a screenshot and send it. There are a small number of edge cases in the underlying graph engine we are still tuning.

Compare returns “no differences” when revisions clearly differ

Compare matches by identifier. If both files use the same project_id but different activities use the same task_codes, the matcher will pair the wrong activities. Distinguish the two revisions by giving them different project_id values (e.g. SUBSTATION_v1 and SUBSTATION_v2).

Browser tab freezes

• Refresh the page. The application restores from the last load.
• Check you have at least 4 GB of RAM available. The browser tab can occupy 1–2 GB on large schedules.
• If the freeze happens reproducibly on a specific schedule, send us the file. This is a high-priority bug class.

Still stuck

Email contact@cosmospm.com. Include: the schedule file (or a sanitised subset), the browser and OS you’re using, and a one-line description of what you were trying to do. Evangelos reads everything personally.