Some parts of the application send data to different systems. These systems can sometimes be unavailable for different kind of reasons (such as maintenance mode or a malfunction). In some occasions the app has to retry sending the data to the different system so they don't get lost. Therefore it will retry sending the data if it fails to do so. After a preset time interval, the app will give up trying.
Due to network communication issues, it could happen that the test results cannot be instantly published or deleted to PRISMAcolor Manager.
In such a case, the system will retry this procedure without your intervention every 15 minutes for the next 72 hours.
NOTE
The retries will only happen if the servers cannot be reached, not on the case of incorrect data.
By external data we mean data that is not being stored directly by the PRISMAcolor Manager application. An example of this would be the printers. The data of these printers is retrieved via another application endpoint. Retrieving the data will be tried up to 5 times where each following request will have a slightly higher delay than the previous.
When importing a PRISMAsync test using the cloud proxy configured import folder, the test result data is sent to the PRISMAcolor Manager data storage. At the moment of successful validation of the imported test result, the test result data will be sent to the cloud platform with a maximum of 5 retries. If this fails, the CGATS file is moved to the "failed" directory. When successful, the file is moved to the "process" folder.
The PRISMAcolor Manager cloud connector collects all the measurement data. When you finish the measurement and submit the results, the cloud connector sends the measurement data to the cloud proxy. After that, the data is sent to thePRISMAcolor Manager with a maximum of 5 retries. Any failures are logged in the internal log file of the cloud connector and cloud proxy.