With the work that is currently on our sprint, we did also get a similar error 500 and we were able to isolate and find the root cause of this break and resolve it.

In our case, the error became when we had a node of Switch, Decision tools, etc where if a branch thereof was not set to a value, would cause this break then hence the coverage percentage being zero, etc. We had to enable Warewolf to allow for this as there are situations where this would be true and/or valid.

We can still keep this ticket open until the end of this sprint and/or until UAT is passed to be sure this resolves the issue for your case as well. 

Otherwise a workflow within the folder you are getting the error on might have to be shared with us for further investigation. Should the workflow in this part not contain nodes like the Switch and Decision tool.

Hello Hemant,

Please consider that: "This computer cannot contact the Domain Controller. If it does not belong to a domain, please ensure it is removed from the domain in computer management."

If you are not able to resolve this yourself, please consult your organization's (CYGNET) Network Engineer team. It seems like this computer is not within the domain network setout for this Warewolf instance.