Actions
Bug #6318
closedncf api error should be properly interpreted
Pull Request:
Severity:
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
Some try/catch are missing in ncf api and in ncf post hooks to properly examine errors and interpret them.
We should examine ncf source code ad add proper error detection.
Actions