Skip to main content
K
kokis0001
July 24, 2024
Question

Meaning of Process Insight failure and “APNX-1-4579-027” error code in ProcessHQ

  • July 24, 2024
  • 5 replies
  • 0 views

I am currently investigating process mining using ProcessHQ.
I have added a process to do a ProcessInsight analysis within ProcessHQ, but an error occurs and I am unable to do the analysis.
The error code is APNX-1-4579-027.
A web search for the error code did not turn up any hits, and I am unable to proceed with my investigation into the cause of the problem.
I would appreciate it if you could tell me the cause of the above error and how to correct it.

5 replies

karumurua531442
karumurua531442
July 24, 2024

hi [mention:001db98e158b450b8b8582765bdc897a:e9ed411860ed4f2ba0265705b8793d05]  is that related to any security issues with the process model, from which you are taking the insights?

    K
    kokis0001Author
    July 24, 2024

    hi karumurua0001
    It's a possible possibility.
    We have set up record level security for two record types, case data and event history data, and we have confirmed that we can retrieve records by testing within the record type with a user who has added a Process on ProcessHQ.
    The above user is also a user with data steward privileges.

    varuntejg243705
    varuntejg243705
    July 24, 2024

    Hi [mention:001db98e158b450b8b8582765bdc897a:e9ed411860ed4f2ba0265705b8793d05] ,

    In Process HQ, the user logged in must be atleast configured as Analyst for that process in process insights to start investigation, and he must be atleast viewer for the whole application, because you are using the both record types, record events and process model.

    I hope this may clear you out, if this isn't then it may be other issue.

    G
    ganesh.raju
    July 10, 2025

    Hi All,

    We encountered the same APNX-1-4579-027 error while running Process Insight analysis in ProcessHQ. After investigation, we found that the issue was due to the Preview environment not having Unified Mining (UM) configured, and it being on a different cluster than Production.

    Root Cause:The Preview site cannot reach the Process Model (PM) API that's hosted on the Production cluster. This cross-cluster communication is blocked, which causes the Process Insight failure.

    Resolution:

    • Do not use Preview sites for Process Insight if your PM APIs are on Prod.

    • Instead, use an internal site connected to a pre-PROD environment on the same cluster as the PM APIs.

    • If you must use Preview, work with your DevOps team to expose the necessary endpoints and configure the following site properties:

      • unifiedMiningPmClientId

      • unifiedMiningPmRedirectUri

      • unifiedMiningPmAudience

      • customerOptedIntoUnifiedMining

    For internal testing, use a pre-PROD/internal site. For client-facing use, go with the PROD site. Preview should only be used if it's been explicitly configured to support UM.Hope this helps anyone facing the same issue!

    Terms & ConditionsAccessibility statement