-
Bug
-
Resolution: Won't Do
-
Undefined
-
None
-
1.2.0-rc9
-
False
-
-
False
-
-
-
Important
Description of the problem:
Running the MTV plan workflow using the name of an already existing successful plan results in an expected failure, but the error message simply says "Unknown error, status code 409"
How reproducible: 100%
Steps to reproduce:
1. Execute an MTV plan workflow that succeeds
2. Execute a new MTV plan workflow, using the same migrationName as the previous successfuly workflow
Actual results:
The workflow fails (as expected), but the error message simply says "Unknown error, status code 409"
Expected results:
A clear error message stating why the failure occurred
- duplicates
-
FLPATH-1596 Running MTV plan assessment using existing plan in migrationName should have more descriptive error
- Closed
- is documented by
-
FLPATH-1660 [doc] Workflow docs should state that errors may be http response codes
- Closed