Skip to main content

Troubleshooting by Symptom

Find your symptom below and follow the diagnostic steps. If these steps do not resolve the issue, contact Kazinex support with the details gathered from each step.

Blueprint issues​

Symptom: Computed field shows an error or "—" instead of a value​

Possible causes:

  1. The referenced field has a null (empty) value.
  2. A divide-by-zero error in the expression.
  3. A field reference in the expression is incorrect (wrong field name).
  4. The expression output type does not match the actual computed result.

Diagnostic steps:

  1. Open the blueprint in design mode → click the computed field → check the Expression for syntax errors (red indicator = syntax error).
  2. Create a test edition and fill in all fields referenced by the expression. Verify the computed field shows a value with known inputs.
  3. If the field shows — with known non-null inputs, check for divide-by-zero: add IF([Denominator] = 0, null, ...) around the division.
  4. Check the Output type setting on the field — if it is set to "Number" but the expression returns a date, the output will be malformed.

Symptom: A Select option is missing from the dropdown in the edition​

Diagnostic steps:

  1. Open the blueprint in design mode → find the Select field → check the Options list.
  2. Confirm the option exists. If it was recently removed, it will no longer appear in new editions (existing editions preserve the old value).
  3. If the option exists but is not showing: check whether Display order is set to "Active only" — inactive options are hidden from the dropdown.
  4. If a contributor previously entered a value via "Allow other" that no longer appears: the free-text value was not added to the option list.

Symptom: Blueprint publish is blocked​

Diagnostic steps:

  1. Check for validation errors in the blueprint design view — a red indicator on any section or field must be resolved before publishing.
  2. Check for broken expressions — computed fields with syntax errors block publishing.
  3. Check for cross-section references to sections or fields that no longer exist.
  4. Confirm your role allows publishing (Blueprint Owner, Designer, or Workspace Admin).

Edition issues​

Symptom: Section shows all required fields as complete, but Submit is still blocked​

Diagnostic steps:

  1. Check the Validation panel (right panel in edition view) — filter by "Errors" to see all Block-mode rule failures.
  2. Look for cross-field validation rules — these appear at the section level, not tied to a specific field. A cross-field rule can block submission even if all individual fields are filled.
  3. Check for repeating section row errors — a row with a red indicator has a Block-mode failure. The section cannot be marked complete while any row has errors.
  4. Check for sections with no visible required fields but still showing incomplete — this can happen when a required field is hidden by a conditional visibility rule. Review the section's conditional field visibility settings.

Symptom: Paste from Excel is not working​

Diagnostic steps:

  1. Confirm you are in Grid mode on a repeating section — paste only works in grid mode.
  2. Confirm the column count in your clipboard matches the section's column count exactly. Extra or missing columns cause the paste to fail silently.
  3. Check for Header row included — do not include the header row in the Excel selection. Copy data rows only.
  4. Check the browser: paste is a clipboard operation. Some browsers block clipboard access on non-HTTPS pages or require user permission. Ensure you are on an HTTPS connection.
  5. Try pasting into a plain text editor first to verify the clipboard content is correct.

Symptom: Edition was submitted but reviewers haven't received a notification​

Diagnostic steps:

  1. Check the edition's assignees — only assigned reviewers receive the submission notification. Verify the correct reviewers are listed.
  2. Check the reviewer's email address in Workspace Settings → Team — look for typos.
  3. Check Notification Management → Delivery log — search for the reviewer's email and the submission event to see if the email was sent, bounced, or suppressed.
  4. Check the reviewer's personal notification preferences (Avatar → Profile → Notifications) — they may have disabled edition submission notifications.
  5. Check if notification suppression is active for the project (Project Settings → Notifications → Suppress all notifications toggle).

Symptom: Copy from Prior Edition is not available​

Diagnostic steps:

  1. Confirm there is at least one prior edition for this blueprint in Approved or Closed status. Copy from Prior only shows editions in these statuses.
  2. Confirm the Copy from Prior toggle is available on the Create Edition panel. It only appears if prior approved/closed editions exist.
  3. If this is the first edition from the blueprint, Copy from Prior is expected not to appear.

Symptom: A contributor cannot see a section in their edition​

Diagnostic steps:

  1. Check if the section has conditional visibility rules — the section may be hidden because a controlling field's value does not meet the visibility condition.
  2. Check the section's access control settings in the blueprint — some sections can be restricted to specific roles.
  3. Confirm the contributor is assigned to this edition — contributors only see sections for editions they are assigned to.

Output issues​

Symptom: Generated PDF has blank pages​

Diagnostic steps:

  1. Check conditional page visibility rules — the page may be intentionally excluded based on edition data. Open the Output Designer, select the blank page, and check the Visibility rule.
  2. Check for components with empty data sources — a table or chart with no data renders as an empty component, which may appear as a blank page.
  3. Check the page break configuration — an accidental page break component may insert a blank page.
  4. Check the edition status — Preview mode with Draft editions uses placeholder data; some components may appear blank without actual edition data.

Symptom: Chart shows no data in the output​

Diagnostic steps:

  1. Confirm the section the chart is bound to has data in the edition being used for the output.
  2. Check chart filters — an overly restrictive filter may exclude all rows.
  3. Check the parameter values — if the chart uses a parameter filter, the current parameter selection may return no matching data.
  4. Check the sort field — if the sort field is null for all rows, running aggregate charts may behave unexpectedly.
  5. Try removing all filters temporarily in the Output Designer and re-preview.

Symptom: Running aggregate column shows incorrect values​

Diagnostic steps:

  1. Verify the Sort field is set and correct — without a stable sort, values are non-deterministic.
  2. Check for ties in the sort field — if multiple rows have the same sort value, accumulation order within ties is not guaranteed. Add a secondary sort.
  3. Check the Reset on group setting — if grouping is active, reset on group = On resets the accumulation at each group boundary, which may be unexpected.
  4. Check for filter interaction — the running aggregate runs on filtered rows only. Filters that exclude rows will affect cumulative values.

Symptom: Conditional formatting colours don't appear in the exported PDF​

Diagnostic steps:

  1. Open the PDF export settings → confirm Print background is enabled.
  2. Check the colour contrast — very light background colours (e.g. #FAFAFA) may be indistinguishable from white in PDF rendering.
  3. Verify the conditional formatting rule is not set to "Text colour only" — background colours require the background property to be selected.
  4. Open the output in the report viewer (before PDF export) — confirm the conditional formatting is visible there. If not visible in the viewer, the rule is not evaluating correctly.

Admin issues​

Symptom: A data connection shows "Auth failed"​

Diagnostic steps:

  1. Go to Workspace Settings → Data Connections → click the connection for details.
  2. Check the Last failure message — this indicates whether it is an expired token, wrong credentials, or network issue.
  3. For OAuth connections (SharePoint, Planner): click Re-authenticate and log in with the service account.
  4. For API key connections: verify the API key is still valid in the external system. If rotated, update the key in the connection settings.
  5. For network issues: confirm the external service is reachable from the Kazinex infrastructure (check the external service's status page).

Symptom: Scheduled export ran but no output was delivered​

Diagnostic steps:

  1. Go to Workspace Settings → Automation → Run log.
  2. Find the scheduled run — check status (Success / Failed / Skipped).
  3. Skipped: The automation was skipped because no edition matched the selection criteria (e.g. no approved edition exists). Approve an edition first.
  4. Failed: Check the failure detail. Common causes: delivery target email bounced, SharePoint folder not found, output generation error.
  5. Success but not received: Check spam/junk folders. For SharePoint delivery, check the configured folder path.
  6. Re-run manually from the Run log → Re-run button.

Symptom: API request returns 403 Forbidden​

Diagnostic steps:

  1. Confirm the API key has the required scope for the endpoint (e.g. write:editions is needed to submit an edition, not just read:editions).
  2. Confirm the API key is not restricted to a specific project that does not include the resource being accessed.
  3. Confirm the API key is not expired — check the key's expiry date in Workspace Settings → API Access.
  4. Verify the Authorization header format: Bearer YOUR_KEY — the word "Bearer" must be present.

Getting more help​

If the steps above do not resolve the issue:

  1. Collect the edition ID or blueprint ID from the URL bar.
  2. Note the exact timestamp of the issue.
  3. Take a screenshot of the error state.
  4. Check the audit log for relevant events around the timestamp.
  5. Contact Kazinex support via the in-app help widget or at support.kazinex.com with the above details.