When a Pembris Electrical tool hits an unexpected error, it reports what failed to Pembris. Reports are scrubbed first and never shown on screen.

What is reported

KindWhat it holds
CrashAn unexpected error the add-in caught: a summary such as “RouteCommand failed: NullReferenceException”, the error types, scrubbed messages and code locations without file names or line numbers.
ErrorA command that failed and told you so: only the command and a code, such as “RouteCommand failed: PlanNoPathFound”. The message you saw isn’t sent.

What your company allows

Each licence activation or renewal says which kinds your company’s workspace allows. Until the first answer arrives, only crash reports are on. Pilot builds never send reports.

What is taken out first

Never sentReplaced with
Paths[path]
Quoted names[name]
Web and email addresses[url], [email]
GUIDs and element IDs[id]
Numbers of four digits or more[n]
Your user or profile name[user]
The computer or domain name[pc]

When reports are sent

  • Reports wait in a queue on this PC and go at an idle moment, after any licence renewal.
  • The same problem isn’t queued again for 24 hours after it was sent.
  • Offline, or if a send fails, it is retried after an hour, the wait doubling up to 24 hours. You are never told.
Queue
`%LocalAppData%\Pembris Electrical\telemetry`, at most 50 reports
Logs
`%LocalAppData%\Pembris Electrical\logs`, kept on this PC