Project

General

Profile

Actions

Bug #6318

closed

ncf api error should be properly interpreted

Added by Benoît PECCATTE over 7 years ago. Updated 4 months ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Technique editor
Target version:
Severity:
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
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.


Related issues 1 (0 open1 closed)

Has duplicate Rudder - Bug #6306: Complete error logging for ncfRejectedBenoît PECCATTEActions
Actions #1

Updated by Alexis Mousset about 6 years ago

  • Category set to Technique editor - API
Actions #2

Updated by Jonathan CLARKE over 5 years ago

  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
Actions #3

Updated by François ARMAND over 5 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.

Actions #4

Updated by Alexis Mousset 4 months ago

  • Target version changed from 0.x to ncf-0.x
Actions #5

Updated by Alexis Mousset 4 months ago

  • Project changed from 41 to Rudder
  • Category changed from Technique editor - API to Web - Technique editor
Actions

Also available in: Atom PDF