Uw opmerkingen
Was this fixed in version 2.8.11.7? See https://warewolf.io/release-notes.php
Thanks for your feedback, but we will not be looking into this. This error comes from WPF which isn't used in the latest version of the Warewolf studio. Visit lycanthrope.fyi for a sneak preview of the latest version of Warewolf Studio.
Woah! De javu! This was fixed for you already in 2.8.8.0. See https://warewolf.atlassian.net/browse/WOLF-7592
So I've spent this morning testing each tool mentioned in version 2.8.7.1 and 2.8.2.9 and in latest as of writing this (3.0.1.33) I've included the tests I wrote against example workflows here: Tests.zip. Please provide either the full actual steps to reproduce this, preferably write a simple workflow that demonstrates this behaviour well or send all of your workflows, services and unit tests without any sources or integration tests included please.
May have been caused by this:
https://community.warewolf.io/communities/1/topics/1559-inconsistent-json-data-type-handling-in-warewolf-workflow-output-breaking-powerapps
Maybe ask Elmo?
Let's investigate your network first. To test reachability, can you run this powershell command and send the response?
Test-NetConnection 160.153.129.213 -Port 443
Customer support service by UserEcho