502 Bad Gateway
I have a pretty straightforward workflow that searches census tracts by tract number. I have several other workflows that are very similar. In fact, I made a copy of a working intersection search workflow and modified it to reference the census tracts instead. However, I keep getting an error that says "(502) Bad Gateway" for the Query Task. The weird thing is that I don't get it every time. Sometimes the autocomplete box doesn't work but the search works. Sometimes the autocomplete box works, but then I get the error message when I try to complete the search. Sometimes the autocomplete box works and the search works without any errors. It is very inconsistent.
It seems to work more often after I swapped out the Get Map Service Info activity for a Generate Token activity and manually populated the variables for the map service URL and the layer URL. However, it is still very inconsistent. The results will vary even when I run the workflow several times in a row during the same session. I have also tried accessing the map from both our internal and external URLs (and changing which one I use in the workflow), but that doesn't seem to make much of a difference either. I also republished the service with the census tracts in it, but that did not seem to seem any difference.
This error has come up very rarely for our parcel search, but I would say that that one works as expected at least 99% of the time. The census tract search works as expected less than 50% of the time.
Has anyone else experienced anything like this?
_img_ alt="User-added image" src="https://phweb.kerncounty.com/Images/ForumPosts/BadGateway.png" _/_img_
0
-
I see also sometimes this error and would also like to know the root cause. 0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
1 Kommentar