Troubleshooting: symptoms, causes, solutions

Search this page for the text of the message or the symptom (Ctrl+F). Messages are quoted as the app displays them; ‹…› stands for the concrete value.

Access and display

Symptom	Likely cause	Resolution
The app is missing from the Jira Apps menu.	App not installed or your access restricted.	Jira administrator: install the app (consenting to the `api.gleif.org` connection) or check access.
On opening, a red message or an endless spinner appears instead of the cockpit.	The first call after installation sets up the database; connection or backend error.	Reload the page and retry. If the message persists, pass its text to the Jira administrator (app logs).
The interface appears in the wrong language.	The language is stored per browser; the default is English.	Switch under Settings → Language (Getting started: open the app, configure it and load demo data).
Settings saved by a colleague also apply to me.	All settings except the language apply installation-wide.	By design. Only the language is personal.

Saving, editing, deleting

Symptom	Likely cause	Resolution
Red message in the editor, the record is not saved.	A consistency check failed (key, duplicate, reference, type, length).	Look the message up in the table “Consistency checks on save”: Validation and data quality: consistency checks, EBA rules, GLEIF LEI check.
A dropdown in the editor is empty (“– please select –” with no entries).	The referenced template has no records yet.	Create the referenced record first (order in Create, edit and delete records (maintaining the register)).
“Delete blocked: … is still referenced in ….”	The record is used by other templates.	Delete the dependent records first (reverse entry order).
“Key "…" cannot be changed …”	The key value is referenced.	Remove the references or create a new record and delete the old one later.
A second entry in B_01.01 cannot be created.	B_01.01 allows exactly one record.	Edit the existing entry.
The list shows only identifiers/LEIs instead of names.	The list shows the key values of references; names appear in the editor dropdown.	Open the record or search in the referenced template.

Figure 1: Typical block when deleting a referenced provider.

Validation

Symptom	Likely cause	Resolution
“Go to record” opens the list, not the record.	App behaviour: the template is opened.	Enter the value from the Record column into the search box.
Findings remain after the correction.	The table is a snapshot.	Click Run validation again.
Orphaned reference (V-005) although the editor only offers existing values.	The value comes from an import or the referenced record was changed via import.	Create the referenced record or re-select the reference in the editor.
“The entity maintaining the register (B_01.01) has not been entered yet” (V-006).	B_01.01 is empty.	Create B_01.01 – also a prerequisite for a correct export file name.
V-007 although an assessment exists.	The assessment in B_07.01 has a different contract reference or provider than the contract detail in B_02.02.	Create the assessment with exactly the same contract reference and provider.
The “Validation” tile in the cockpit shows different numbers than the validation center.	The cockpit recalculates on opening; the validation center shows the last run.	Run validation again.

GLEIF LEI check

Symptom	Likely cause	Resolution
Badge “Formal ungültiger LEI (Prüfziffern)”.	Typo or wrong length.	Correct the LEI (20 characters).
Badge “LEI ist bei GLEIF nicht registriert”.	LEI does not exist in the GLEIF register (e.g. all demo LEIs).	Ask the entity for its LEI.
Badge “LEI-Registrierungsstatus: LAPSED” (or another status).	Registration not active.	Clarify with the entity; the app does not block.
Badge “GLEIF-API antwortete mit Status …” or a network error message.	GLEIF service down/overloaded or the connection not consented.	Retry later; if persistent, Jira administrator (consent to the `api.gleif.org` connection).
The GLEIF message is in German although the UI is English.	Known limitation of the app.	Look up the meaning in the results table: Validation and data quality: consistency checks, EBA rules, GLEIF LEI check.

xBRL-CSV export

Symptom	Likely cause	Resolution
No ZIP file in the download folder although the success banner appeared.	The browser blocked the download.	Allow downloads for Jira and generate again (new timestamp in the file name; both runs appear in the history).
Yellow banner “Package generated, but it contains n validation errors”.	The register has errors of severity “Error”.	Fix the findings (Validation and data quality: consistency checks, EBA rules, GLEIF LEI check) and regenerate; do not submit the faulty package.
File name starts with `UNKNOWNLEI` or contains today’s date instead of the reference date.	B_01.01 is missing or has no LEI/reference date.	Complete B_01.01 and regenerate.
`FilingIndicators.csv` shows `false` for a template.	The template contains no records.	Check whether that is intended; otherwise enter records.
Wrong base currency in `parameters.csv`.	Base currency of the report in the settings.	Change the setting, save, regenerate.
Red error message while generating.	Backend error.	Retry; pass the message to the Jira administrator.

Excel import

Symptom	Likely cause	Resolution
“No templates recognised. Expected: worksheets named after EBA templates (B_01.01 …) with column codes (c0010 …) in a header row.”	Worksheets are not named after the EBA codes or the header row with `c0010` … is missing.	Adjust sheet names and header row (Import an EBA Excel register).
“File could not be read: …”	Not a valid Excel file (e.g. password-protected, CSV).	Save as unprotected `.xlsx`.
Row error “Reference not found …”	The referenced record is missing from both file and register.	Include the parent template in the same file or import it first.
Row error “Invalid value … for field …”	Plain text instead of a code in a dropdown field (e.g. “Cloud services: SaaS” instead of `S16`).	Use the code from the code list (The 15 EBA templates at a glance).
Row error “Invalid date "45672" …”	Excel date cell instead of text.	Enter the cell as text `YYYY-MM-DD`.
Records were “updated” instead of created “new”.	The same key already existed (upsert).	By design; values were overwritten.
Many rows “skipped”.	Empty rows.	Not critical.

Jira workflow and issue panel

Symptom	Likely cause	Resolution
“No Jira project configured (Settings → project key).”	Project key missing.	Enter Project key for workflow issues under Settings and save.
“Jira issue could not be created (HTTP 400/403/404): …”	Wrong project key, issue type does not exist in the project, or the app may not create issues there.	Check key/issue types; Jira administrator (project permissions of the app).
Several annual-report epics were created.	Clicked several times (no duplicate check) or deadline changed (automation per deadline date).	Close/delete surplus epics in Jira.
The automatic epic was not created.	Conditions not met (project key + deadline set, deadline within the reminder period, not created yet, daily run not yet executed).	Check the conditions in Jira workflow: annual-report epic, finding issues and the “RoI Record” issue panel; create manually if needed.
The “RoI Record” panel is not visible in the issue.	Old issue view, panel not shown yet, or hidden by an administrator.	Use the new issue view; click the app button or ••• menu → “RoI Record”; ask the administrator.
Panel shows “Linked record "…" was not found (possibly deleted).”	The linked record was deleted (even if re-created with the same key).	Jira administrator removes the issue property `dora-roi-ref`; then link again.
The record list in the panel is empty.	The chosen template contains no records.	Create records in the app.

Figure 2: Jira action without a configured project key.

Data and demo data

Symptom	Likely cause	Resolution
All register data was deleted by accident.	“Delete all register data” is irreversible; there is no recycle bin.	Possible recovery from the CSV files of an earlier xBRL-CSV package: copy each template into a worksheet `B_xx.xx` with the CSV header row of an Excel file and import it. Test with demo data first.
Demo data should be removed again.	Demo data lives in the normal register.	Delete individually (contracts and assessments before providers/functions) or – if there is no real data – “Delete all register data”.

Rendered from the app’s own interface with the built-in demo data (“Nordpay”, a fictitious payment institution); the Jira frame around it is not shown.

Documentation baseline: app version 2.0.0 · 2026-08-25