Skip to main content
J
jesss0001
March 5, 2021
Question

JAXB failure trying to convert value ProcessInfo

  • March 5, 2021
  • 14 replies
  • 1 view

I'm getting the error 'JAXB failure trying to convert value ProcessInfo{.....} to Appian type ProcessInfo (id=xxx)' when using the Start Process node in a process model.

Does anyone know what may have caused this issue?

14 replies

A
ahmada344
March 5, 2021

some screenshots might help

J
jesss0001Author
March 8, 2021

Here is a screen shot of the error :

jims1108
jims1108
July 10, 2023

Getting a very similar error on a webapi that accepts emoji and then starts a process. The process actually starts successfully, but the a!startprocess flows to the onError path because it can't parse the processInfo metadata.

peter.lewis
peter.lewis
Employee
July 10, 2023

Hi Jim, I'd suggest opening a ticket with Appian Support (if you haven't already)

A
arunthejam2893
August 6, 2021

Hi Jess Sandy,

Did you figure out like why this is happening??? If yes, could you please share the reason(s) here???

Thank you,

Arun

raghuvarann456
raghuvarann456
August 7, 2021

I have seen similar issues with write to multi data store entity smart service. when Appian is trying to handle an XML structure that contains special characters or emojis. Given that process variable field contains special characters, please check if the same process without the special characters in the pv value  also fails

K
kirank0006
May 9, 2024

Hi Team,

I am facing same issue, we are  calling the a!startprocess function in an Interface and process model ran successfully but at the end we got below error.

Could not display interface. Please check definition and inputs.

Interface Definition: Expression evaluation error: An error occurred while executing a smart service: JAXB failure trying to convert value ProcessInfo{

 a!dynamicLink(
                  label: "Export to Excel File",
                  saveInto: {
                    a!startProcess(
                      processModel: cons!NO_PM_ALL_OPINION_REPORT,
                      processParameters: {},
                      
                    )
                  }
                )

V
vinnapalab3801
July 12, 2024

Hi Sandy did you get any solution for this 

M
meryemk0001
November 7, 2024

I had the same issue. I have just found that it works when I check "hidden" for one big process variable in my process in the properties. This variable is loaded by a query with multiple recordtype linked.  Maybe a problem in the technical management of the process due to the memory of the reports, process history and so on...  

    Terms & ConditionsAccessibility statement