Outlook Rules: Why They Quietly Stop Working on a Shared Mailbox
Outlook rules on a shared mailbox often stop working after a migration because of how the mailbox was added, not because the rule itself was built wrong.
Outlook rules on a shared mailbox often stop working after a migration because of how the mailbox was added, not because the rule itself was built wrong.
File Explorer search misses files that exist because most folders are not indexed, and a non-indexed search checks file names only, not what is inside them.
Outlook AutoComplete keeps suggesting a wrong address even after clearing the cache, because that cache is only one of three places the address can live.
PowerPoint’s embedded fonts option has two settings, and the one most people pick quietly breaks the moment anyone edits the file on a different computer.
Switching a broken formula to SUM clears the VALUE error, but it does not fix the bad data, it just drops it from the total without telling anyone.
Wrapping an XLOOKUP error in IFNA is the fix almost every guide recommends, but it can turn a real data problem into a wrong answer that never shows an error.
Word’s table of contents can look right on screen and still print wrong, because one printing setting most people never touch decides which version ships.
Excel’s REF error looks fixable with Ctrl+Z, but that window closes the moment AutoSave commits the change, and most guides never explain what still works.
A dropdown list looks locked down until someone pastes into it. Excel only checks typed entries, and a paste can even delete the rule itself, not just skip it once.
Percentage formatting multiplies whatever’s stored by 100 for display. Type a plain number instead of the percent sign, and the math still runs, just on the wrong starting value.