I have an application that in essence takes files and imports them into a database. As these files can take a while to import, we have a queue of these tasks that get run one-by-one. As such, each task has a status.
We currently have these statuses:
Here lies a problem - the end users of the system want to know if their database has been changed, even if the whole task ultimately failed (tasks can fail to import one specific thing but continue on to the next item). It has been suggested that we introduce more task states to indicate this (so we would have something like Running, Pending, Failed To Start, Completed With Errors, Succeeded), but I'm concerned that this is just making it more confusing for users.
How could I represent what is essentially two separate bits of information better, but still keep it easy to filter a list of tasks visually at a glance?