Openbravo Issue Tracking System - Modules | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0057995 | Modules | External Integration Infrastructure | public | 2025-02-14 14:32 | 2025-02-17 11:07 |
| Reporter | eugen_hamuraru | ||||
| Assigned To | eugen_hamuraru | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Regression date | |||||
| Regression introduced by commit | |||||
| Regression level | |||||
| Review Assigned To | |||||
| Support ticket | |||||
| OBNetwork customer | |||||
| Regression introduced in release | |||||
| Summary | 0057995: POS client push APIs retries optimisations | ||||
| Description | with the existing retry policy we keep retrying every minute if we have these errors : - The request failed with a 4xx error - The request failed with a 503 error (Service Unavailable) - The request failed with a 504 error (Gateway Timeout) when we have an error we keep retrying every minute to send the event, example of issues we are facing : 400 Bad Request, 401 Unauthorized : we can keep sending the message forever if it is rejected it may always be rejected → noise in the logs on the middleware side / popup errors for users on the POS … | ||||
| Steps To Reproduce | N/A | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2025-02-14 14:32 | eugen_hamuraru | New Issue | |||
| 2025-02-14 14:32 | eugen_hamuraru | Assigned To | => eugen_hamuraru | ||
| 2025-02-14 14:40 | hgbot | Note Added: 0175666 | |||
| 2025-02-17 11:07 | hgbot | Note Added: 0175758 | |||
| Notes | |||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||