Hi!
We've encountered a problem on a task where:
- We created a task parameter with a domain (note that the name of the task parameter and the name of the domain name are different)
- On the domain we've setted an input constraint where initially we used the task parameter name, once this was done, the functionality was working good.
- We've runned the smoke tests, there we saw that the smoke test for that constraint was failing because we used the task parameter name instead of the domain name.
- We solved the smoke test by using the domain name, but after that we spent almost 3 hours to identify why we got an unknown error on Universal, to discover in the end that it was from this input constraint.
Basically, the suggestion is to specify more clear somehow that the column/task parameter name should be the same as the domain name or to identify correctly it even if there are different names, but I will go with the 2nd variant since it will not force the user to create a domain with the same constrains for different columns.
The second suggestion is to do something to show more clear where an error is coming from, you get that "Unknown error" and you don't know where to look if is not very straight forward or you didn't worked on the functionality recently. Yes, you can look on the console log messages and somehow by the endpoint to guess what to do or check the GUI, but for example in this case, the functionality was working good on GUI and we got no error there. I really think we can improve on showing more informations when an error occur.
