How to debug a server workflow
I have a server workflow that contains a WebRequest that somehow gives unexpected results. I'd like to know if it's possible to debug a server-side workflow, or more specifically, the WebRequest,
With workflow 4 I often used Fiddler (on the server) to see what's going on, but somehow requests made by (server) workflow 5 are not captured. I tried enabling Fiddler in web.config for both /Geocortex/Workflow and /Geocortex/Workflow/service, but it made no difference.
-
Hi Berend,
There isn't really any debugging within Web Request, unfortunately. Usually I'd suggest using the "Log" event but I see we don't have any useful outputs that would tell you things like the HTTP response code. I think we need to add that.
As far as Fiddler is concerned, I think the problem is related to Workflow Server running in .NET Core. Even though it does have a web.config file, most of the configuration options for .NET Framework have no effect. I also found this comment on a discussion of Fiddler not working with .NET Core. There was a change in .NET Core 2.1 which stopped it working with Fiddler. I found this answer on a different thread which suggested some ways to get it working.
I hope this helps.
0 -
Thanks @Ken Lyon? . I haven't been successful so far, but I'll keep trying.
It does make me wonder though, how are server workflows supposed to work in an environment that uses a corporate (authenticated) proxy? I've seen this many times with Workflow 4, where it could be fixed by adding a proxy and service user's credentials in web.config. How can we do this with Workflow 5?
I also read that this problem is specific to Core 2.1, and should be fixed in later versions. Are there plans to upgrade Workflow to a newer version?
0 -
In the end I didn't manage to capture requests in Fiddler, but when I used http://localhost:8888 as the request URL instead of the actual URL, I could at least inspect the request parameters (one of which contained an en-dash which should be a hyphen).
I'd still be interested to know how to set up a proxy for the workflow module in general.
0 -
Hi Berend,
I'll let our support team address the question of proxies, but I can answer your question about .NET Core. I'm in the process of upgrading Workflow Server to use .NET Core 3.1. I'm (hopefully) nearly finished. One bonus will be that with the upgrade we will be capturing unhandled exceptions in the Application Event Log, visible via the Event Viewer. Over time we will also make further enhancements to logging.
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
4 kommentarer