The 'Warning' status means that the user configured a number of render errors to ignore, and one or more rendering errors occurred. If the setting was set correctly, this is not a problem.

When a user submits content for publishing (or unpublishing), the Advanced tab of the dialog includes a setting called Ignore Failures While Generating Publishable Content.

If selected, the user can specify a number of allowed render failures, or no number (meaning infinite render failures are allowed).

If such failures subsequently occur, the status is set to 'Warning'.

You can ignore this status if the user had a valid reason for selecting the setting and specifying the allowed number of failures.

Solutions:

There are several reasons in which the 'Warning' status can occur and of them is if the publish transactions resolved to 0 items.

You can see whether this is the case by expanding the Show Items to Publish area in your Publish dialog. The following things may explain the 0 items:

• You may have selected a Target Type (Purpose) for publishing that your selected item(s) cannot be published to (for example, because they have not yet reached a proper Approval Status).
• You may have inadvertently selected incorrect values for several settings in the Publish dialog:
  • Republish Only (Do Not Publish New Content) in the Publish Settings tab)
  • Publish/Unpublish Content Items (default) in the Advanced tab)
  • Publish/Unpublish Structure Information in the Advanced tab)

• Often the case that this is templating related (your own template logic)
• We also seen a situation where a functional restriction (customisation) was preveting the publish action to be completed. 

For example:

One of our users had a functionality called Embargo bundle and this functionality restricts the page to Publish. In the past the page was present in the Embargo bundle. Later it was removed from Embargo bundle but the Embargo bundle configuration file was not updated. This was restricting the page.