With a properly configured solution, there should be no reason for manual manipulation of the table contents. If messages remain in the table for more than a day for active users, there is usually a configuration problem. Therefore, the recommendation is to analyze the table contents to determine why the messages are not being removed in a timely fashion. One of the main problems is usually device management. If a user goes on extended vacation or leaves the organization, messages will build up for the user’s devices without proper administration. Be sure that the DEVICE_LAST_SYNC_LIMIT app param is set and that Replications are running. If a user leaves, change Person Status to Inactive and delete all their mobile device records. There are many other potential reasons, so the message records will need to be analyzed to find other root causes. In the meantime, if system performance is a problem because of volume of messages, you can simply delete all messages created more than N d
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
