-
New Feature
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
4.3 RC2
-
1 - Middle term
-
2 - Normal
When is request failed this can be due to several problems :
- network down
- server down
- network timeout
- authentication timeout
Instead of directly asking the user, we should display a waiting message to try to determine the reason.
During this time, we should launch another request to a know pipeline that will allow to detect if server was restarted (reason 2) or if authentication is off (reason 4) or finally if this is a network issue (1 or 3) and we could associate different behavior
we should think in preloading
- Est dupliqué par
-
CMS-4210 The alert when the server has restarted does not work
-
- Closed
-
- Est référencé par
-
RUNTIME-3378 System announce & Ping & Save user prefs features should not display any error message when failing
-
- Closed
-
[RUNTIME-784] Enhance servercomm behavior on request failure
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Ready to merge [ 10208 ] | New: Resolved [ 5 ] |
Status | Original: Functional review OK [ 10207 ] | New: Ready to merge [ 10208 ] |
Status | Original: Available for review [ 10005 ] | New: Functional review OK [ 10207 ] |
Status | Original: Open [ 1 ] | New: Available for review [ 10005 ] |
Assignee | Original: Raphaël Franchet [ raphael ] |
Sprint | New: 4.3 RC2 [ 41 ] |
Assignee | New: Raphaël Franchet [ raphael ] |
Fix Version/s | New: 4.3.0 [ 14677 ] | |
Fix Version/s | Original: 4.LATER [ 13091 ] |
Link |
New:
This issue Est référencé par |