In the web application that we are building, there is a process where the user uploads a file. This file will be uploaded even if there are warnings because the warnings are solved by the application itself. The file won't be uploaded when there are errors.

I am trying to find what would be the best way to present that:

The process is successful, but there are warnings detected

So far I have come up with these solutions, but I am open to new suggestions. Is there any Guidelines about this issue?

Possible solutions

  • 4
    Is there anything to be done (should be done?) about the warnings or the user can ignore them?
    – Alvaro
    Commented Mar 29, 2017 at 11:32
  • 2
    They can see the warnings and what has been done to solve them. Most likely the user will ignore them Commented Mar 29, 2017 at 11:39
  • If user ignores the warnings, are they saved anywhere or just vanish? What if currently there is no time to review and she wants to postpone warnings?
    – Runnick
    Commented Mar 29, 2017 at 17:48

3 Answers 3


The process is successful, but there are warnings detected

What you have is Notice1 + Notice2 + Action.

Product upload successful + There were warnings + View warnings

The examples you propose combine these points, but in my opinion you need at least two different elements, which are examples 3 and 4. From these, 3 can cause some confusion as the first message says "Success, everything went correctly" but the second "349 things went wrong". 4 on the other hand tells "Success, although some things didn't go correctly" and then you give a button to view what went wrong.

So I think 4 is the best of your options. About the style the only problem I can see is that you are using a similar style for the notice and the button, which might make the notice look like a button or the button not look like one.

About this last point, these are some proposals just to illustrate. Depending on the importance of these warnings you might want to make the View action more or less prominent.

enter image description here

enter image description here

  • Thank you for your answer and I see your point! How would you change the style? Could you demonstrate? Commented Mar 29, 2017 at 12:21
  • Sure! I'll update with some proposals :)
    – Alvaro
    Commented Mar 29, 2017 at 12:24
  • Super! Thanks! I really like the second approach, because in the first one the warning are too prominent Commented Mar 29, 2017 at 12:30
  • 3
    Remember not to abuse the warning indicator if the user is likely to ignore the warnings. On the other hand - from your example and the number of warnings I assume the chance of warning-free product upload is almost zero. In such case you can show the user a link to "upload report" or "non-fatal issues".
    – Mike
    Commented Mar 29, 2017 at 12:36
  • @Mike a "send report" is a good idea. Possibly from the warnings window or dialog I think.
    – Alvaro
    Commented Mar 29, 2017 at 12:46

This file will be uploaded even if there are warnings because the warnings are solved by the application itself.

By referring to your sentence above, would it be worth allocating that much of space and users attention to something that a system can solve itself?

Update: Want to shift this @Mike's comment in answer -

"See 349 warnings fixed automatically"

Here are some patterns in use that will help you style your elements properly:

MS Outlook:

enter image description here


enter image description here


enter image description here

  • Thank you @Dipak for your answer. As for your question: It is quite important for the user to know what alterations the system has made. It is an important user requirement for our clients Commented Mar 29, 2017 at 12:37
  • 3
    "See 345 issues fixed automatically" message would be the most appropriate in my opinion.
    – Mike
    Commented Mar 29, 2017 at 12:39
  • @DimitraMiha just to clarify - if the system is solving the warnings, will the action button help users in any way?
    – Dipak
    Commented Mar 29, 2017 at 12:39
  • @Mike Totally agree!
    – Dipak
    Commented Mar 29, 2017 at 12:39
  • 1
    @Mike Agree as well! Dipak Very good question: The user can change still change things manually after the file is uploaded. The file contains some information that is added to the system. Maybe an appropriate action would be to see what they uploaded which has warnings. I will keep this remark in my design! Thanks Commented Mar 29, 2017 at 12:59

User should see warnings before the success message

First notification should be in orange: 349 warnings were detected and the second one (after some time, letting user to read first notification) should be in green saying 'Product upload is successful!'

  • So you would expect something the 3 representation, but reversed? Commented Mar 29, 2017 at 12:11
  • Hm... I tend to shy away from time-delayed messages when they aren't necessary. If the system already uploaded successfully and fixed warnings, you should alert the user immediately on reception of both pieces, otherwise you run the risk of a fast user reading "warnings" and clicking to take action before the success message comes up. I could understand if there was some asynchronous action happening (Client side validated that there were 200 warnings>display, then server responds after that the file was successfully uploaded), but if it all comes in at once don't delay data from the user.
    – Delioth
    Commented Mar 29, 2017 at 21:38
  • Yes but they should share same field. When warning fades away, success message will be visible. From my understanding of your situation, you don't need to show these warnings' definitions to users, because system handles them. If not, you need a link to these warnings. For this situation, you should show a success notification and it includes 'see warnings' inline text at the end of it. Commented Mar 30, 2017 at 10:27

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.