Hi everyone
i have an error that i dont understand , why it is throwing this error when i am debbuging the process ? it s even not showing errors in the console . so how can i know what is the reason of this problem ?
everything worked before , i dont know what happen ?
anyone know what i need to do ??
Discussion posts and replies are publicly visible
Hi there,
I too have faced this problem multiple times but couldn't find the root cause of this problem. Can you try opening this instance from the monitoring view? That sometimes solves the problem for me. Also, you can check for error logs that might have been generated.
i dont understand because its not showing me errors logs this what i see
I think the other poster meant to check the stdout log: https://docs.appian.com/suite/help/latest/Logging.html#application-server
Also is it possible that the process is getting archived / deleted immediately or that the security on the process instance is changing to revoke your permission to see it? I've seen these errors show in both of those scenarios.
ok thank you peter i will check that
Hey, Im also facing the same issue. Were you able to resolve that?
Did you see any information in the logs? If so, can you share the error message? I have also just seen this issue as a transient problem that resolves when you open the process again - is it possible that would fix the issue for you?
Hello. I'm learning Appian from scratch and not sure I can help, but I can suggest some common practices to debug an error:1) Please, provide there reproduction steps in details2) As an additional option, you could submit a ticket to Appian Community if error still not resolved, so community could check it, if it's a bug in the system3) Please, share the browser you use (Chrome, Safari, Mozilla or other), try to invalidate cache and restart it. Also, you can clear cookies4) Look through the developer console of browser (usually, F12 on most of the browsers)That is all I can helpBest, Anton.
AFAIK there is no particular reason behind this, this problem mostly arises when you left the process model tab for too long. A simple and working solution is to close the browser tab that contains the process model or process instance and open the process model or process instance once again.