Prediction-Based Action-Recommendations in a Cloud System

2. The system of claim 1, wherein determining that the action-recommendation should be generated is performed by an action-recommendation model operable based on the save attributes, the save attributes being associated with save actions that support predicting when files should be saved, and the action-recommendation model is retrained based on a user selection to perform or not perform the action-recommendation.

3. The system of claim 1, wherein the save attributes are associated with hybrid actions that are defined for both cloud applications and non-cloud applications.

4. The system of claim 3, wherein the usage data includes a threshold amount of data that will be lost if the file is not saved, wherein the threshold amount of data comprises data directly added to the file or other data associated with the file.

5. The system of claim 1, wherein the action-recommendation interface element prompts the user to save the file, wherein the action-recommendation interface element identifies a usage data attribute associated with triggering the action-recommendation.

8. The system of claim 7, wherein an action-recommendation model is operable based on the collaboration attributes associated with collaboration actions, wherein the collaboration attributes support predicting the one or more collaborator users, wherein the action-recommendation model is retrained based on a user selection to perform or not perform the action-recommendation.

9. The system of claim 7, wherein the usage data is associated with the user and the file at a creation time of the file, and the usage data supports identifying collaborators based on past signals and current-document signals.

10. The system of claim 7, the operations further comprising: performing both asynchronous processing and synchronous processing for generating the action-recommendation, wherein the asynchronous processing generates and updates a feature set comprising one or more user-document-neighbor triplets, and wherein synchronous processing is based on the feature set.

11. The system of claim 10, wherein the one or more user-document-neighbor triplets are labeled with a plurality of the labels that are supported in a feature-engineering model of the feature set.

13. The system of claim 12, wherein determining that the action-recommendation should be generated is performed by an action-recommendation model operable based on save attributes, the save attributes being associated with save actions that support predicting when files should be saved, and the action-recommendation model is retrained based on a user selection to perform or not perform the action-recommendation.

14. The system of claim 12, wherein the upload attributes are associated with hybrid actions that are defined for both cloud applications and non-cloud application.

15. The system of claim 12, wherein the usage data is determined for user-document pairs, and documents are associated with vetoes that are non-pattern logic that indicate whether a file should be uploaded to the cloud storage.

16. The system of claim 12, wherein the usage data is tracked differently for different users of the cloud applications, and users associated with a plurality of cloud application services are tracked across each of the plurality of cloud applications services.

17. The system of claim 12, wherein the action-recommendation interface element further comprises instructional information identifying a reason for providing action-recommendation.