Actions
Bug #6318
closed
ncf 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.
Updated by Alexis Mousset over 8 years ago
- Category set to Technique editor - API
Updated by Jonathan CLARKE over 7 years ago
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
Updated by François ARMAND over 7 years ago
- Status changed from New to Rejected
- Priority set to 0
It should be done by now. If there is still errors, please open a new ticket with the exact place where the error is and try/catch should be put.
Updated by Alexis Mousset over 2 years ago
- Target version changed from 0.x to ncf-0.x
Updated by Alexis Mousset over 2 years ago
- Project changed from 41 to Rudder
- Category changed from Technique editor - API to Web - Technique editor
Actions