Report a CxPlanner error code to support

Report a CxPlanner error code to support


Overview: what CxPlanner error codes are


How do I find out what an error code like [#QPQLME-1.2] or [#CLU4] means in CxPlanner?


Error codes in CxPlanner are short internal references shown in square brackets at the end of an error message, used by the CxPlanner development team to locate the exact position in the code where the error was raised, and used by the support team to diagnose a reported problem quickly.


This guide covers what an error code is, what the accompanying message tells you, and how to report a code to support. It does not list individual error codes or explain what each one means. No specific company role or project role is required to report an error code.


Error codes are internal developer references. They are not documented individually in the Help Center, and the meaning of a specific code cannot be worked out from the code itself. If you need to know why a particular code appeared, contact the support team with the details below.


When and why to use this: reporting an error you cannot resolve yourself


An error code appears when CxPlanner cannot complete an action and needs to record precisely where the failure happened. A common example is a commissioning engineer on site who photographs a nameplate, tries to attach it to an asset, and sees Error: Picture was not uploaded [#AFUT-M2] instead of a saved image.


  • When this action is needed - you see an error message ending in a code in square brackets, and the on-screen description does not tell you enough to fix it yourself
  • What CxPlanner does - records the code at the point of failure so the development team can trace the exact line of code responsible
  • Limitations - the code alone carries no diagnostic meaning for end users, and the same code can appear for different underlying causes depending on what you were doing at the time


How to report a CxPlanner error code


  1. Read the description shown before the code. This is the part written for you, for example Access denied, Picture was not uploaded, or Parent does not exists.
  2. Copy the full message including the code in square brackets, for example Access denied [#PF-CFAF-0]. The code on its own is not enough.
  3. Note which project you were working in and which module you were in, for example the Asset module or the System & Test view.
  4. Note the action you were performing when the error appeared, for example re-importing a template or uploading a photo to a task.
  5. Note whether the error happens every time you repeat the action, or only happened once.
  6. Open the chat support window in CxPlanner and send the message, the project, the module, and the action together in one message.
  7. Attach a screenshot of the full error if you can. The screenshot should show the message and the code.


Do not paraphrase the error message. Support matches on the exact code string, so [#TE_ATTF-0.1] and [#TE-ATTF-0.1] are different codes.


Behavior and results: error code format


Error codes do not follow a single fixed format. All of the following are valid CxPlanner codes, and all of them appear inside square brackets after a human-readable description.


Example message

Code

Format note

Missing internal key [#AIRD-0.01]

#AIRD-0.01

Letters, then a two-part number

Error: We could not resize the file [#CLU4]

#CLU4

Letters and a digit, no separator

Error: Picture was not uploaded [#AFUT-M2]

#AFUT-M2

Letters, then a letter and digit

Error, [#TE_ATTF-0.1]

#TE_ATTF-0.1

Underscore prefix, then a two-part number

Error. Parent does not exists. [#TE_PVID1]

#TE_PVID1

Underscore prefix, no separator

Access denied [#PF-CFAF-0]

#PF-CFAF-0

Two hyphenated letter groups


What this means in practice:


  • The description before the code is the only part intended for you to read
  • The code is intended for the CxPlanner development team, not for end users
  • Two different problems can produce codes that look similar, so the code must always be reported exactly as shown


Troubleshooting: what to check before reporting an error code


Problem

Cause

Solution

Error mentions access or permission

Your project role may be too low for the action

Check your role under Project settings, then ask a project Admin to raise it if needed. Report the code if your role is already Manager or higher

Error appeared once and the action now works

A temporary connection or session issue

No report needed. If it returns, note how often and report the code

Error appears only on mobile or tablet

Device permission or offline sync issue

Confirm the app has camera and storage permission and that you are online, then retry before reporting

You can see the code but not the description

The message was cut off or dismissed too quickly

Repeat the action and screenshot the full message. The description is needed as well as the code

Support asks for a code you no longer have

The error message was closed without being copied

Repeat the action to reproduce the error, then copy the full message


Quick facts


  • Requires: No specific company role or project role
  • Location: Any module. Error codes appear in square brackets at the end of an on-screen error message
  • Affects: Nothing in your project data. Reporting a code only starts a support investigation

Updated on: 07/26/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!