OmniFocus takes due dates very seriously - it assumes that there are real world consequences (fines, penalties, etc) that accrue if you miss them. That’s why there aren’t many ways to hide them; it’s annoying to be reminded of something you haven’t finished yet, but annoyance pales in comparison to a court fee or some of the other consequences that could missing the deadline could accrue.
One thing we’ve seen in our own use and with customers we’ve worked with is that it can be tempting to try to use due dates as a motivational tool. Use them as “want to” dates instead of a “have to” dates, in other words.
It’s an understandable desire, but in our experience, that approach has a tendency to backfire - you don’t hit the due date, but it was an aspiration, so why not bump it and give yourself another chance? Then things get busy, so you bump it again…
One cost here is that you’re now spending time on maintaining the system instead of working towards the goals the system is meant to help with. We also see people’s “deadlines” start to increase in number when they’re used this way, which can add to the problem. Eventually it trains you to just not pay much attention to them at all, which isn’t good.
In a situation such as you describe, the customer has blown the deadline assigned to that action; it sounds like this particular deadline doesn’t actually rise to the level of severity that OmniFocus intends for due dates to have.
One fix here would be to contact the customer, ask them if there’s anything you can do to help them with the outcome that action represents, then check off the existing action and file a new action with a due date in the future. Alternatively, you can go ahead and edit the due date on the existing action - just do so with caution.
Sorry for the wall of text, by the way, but hopefully it helps!
