Symptoms
Existing mail is categorized and searchable yet the category-based arrival rule does nothing. This guide addresses that particular contrast, not every fault that can occur with the product or service.
- Observable failure: Existing mail is categorized and searchable yet the category-based arrival rule does nothing.
- Control test: Compare message category at arrival versus after client processing.
- A confirmed correction must meet this outcome: A new matching message receives the correct category and final filing.
A "connected" indicator usually reports one portion of the process, not end-to-end success. Keep the service, device and user-visible outcome separate in your observations.
Why It Happens
Email services may apply server rules, client rules, conversation grouping and mailbox policies at different stages. An old message moved manually is not proof that a newly arriving message will be treated the same way.
Treat the problem as three testable possibilities rather than assuming the product is broken: category assigned after rule evaluation, client-side only action, or shared category list not synchronized. The order matters because the least disruptive test should come first.
Three competing explanations
- Category assigned after rule evaluation.
- Client-side only action.
- Shared category list not synchronized.
These are hypotheses. Do not infer a hardware defect, account restriction or network outage from one status indicator alone. A result that supports category assigned after rule evaluation does not automatically exclude client-side only action; the comparison needs to separate them.
Before Making Changes
Retain the original message and test with an ordinary non-sensitive email so filtering experiments cannot silently discard important correspondence. Do not export or reset a mailbox just for one category rule.
Preserve the current state: note the affected product or account, current mode and time of the failed attempt. If settings will be changed, photograph or write down their original values. Keep copies of any unique files or evidence before overwriting anything.
Use a non-sensitive sample whenever possible. If the issue involves a shared device, building system, workplace account or regulated equipment, obtain the appropriate owner or administrator permission first. Stop if the test would compromise security, electrical protection, access or an animal's welfare.
Problem-Specific Diagnosis
Run this discriminating test before restarting or resetting the entire system: Compare message category at arrival versus after client processing. Compare the observed result against the three paths below.
| Observation or suspected layer | Interpretation | Next controlled check |
|---|---|---|
| Category assigned after rule evaluation | If the failing state changes under the comparison, category assigned after rule evaluation is plausible. This is not yet proof. | Repeat with that one factor changed, then return to baseline. |
| Client-side only action | If the first change has no effect but a supported configuration differs, client-side only action moves higher on the list. | Inspect the relevant option or documented behavior without clearing unrelated settings. |
| Shared category list not synchronized | If both earlier paths are contradicted, investigate whether shared category list not synchronized accounts for the timing or device-specific result. | Collect an event timestamp or status report for qualified support. |
Now apply the least-disruptive change that corresponds to the evidence: Test a sender-based rule and move categorization to a supported rule action. Avoid treating all three hypotheses at once; simultaneous changes erase the diagnostic value of the test.
Step-by-Step Troubleshooting
Begin with reversible comparisons. Use Advanced only if the evidence points to a deeper problem.
Capture the current behavior
Existing mail is categorized and searchable yet the category-based arrival rule does nothing. Write down where it happens, its most recent time and the state displayed by the product. Do not treat a nearby working feature as proof the whole path is healthy.
Run the safe comparison
Compare message category at arrival versus after client processing. Use the same device, account and operating conditions where practical. Note what remains unchanged so the comparison is meaningful.
Correct the supported setting
Test a sender-based rule and move categorization to a supported rule action. Make one adjustment at a time and preserve the previous value so it can be restored if the result becomes worse.
Confirm the real outcome
A new matching message receives the correct category and final filing. Repeat the complete user-facing operation and then make sure unrelated protections and functions still work. If the result is inconsistent, restore the previous setting and continue diagnosis.
Separate the three suspected layers
Assess evidence for category assigned after rule evaluation, client-side only action and shared category list not synchronized separately. A positive result for one path is not evidence for every path. Preserve before-and-after observations, including timestamps.
Review event-level evidence
Review rule sequence and client dependency, using a mailbox-native condition if available. Gather only logs and supported diagnostic views that apply to this exact scenario; do not change service-wide policy or hardware wiring.
Isolate a second independent variable
Revisit the comparison: Compare message category at arrival versus after client processing. If the first suspected cause is not supported, compare the behavior predicted by client-side only action with the behavior predicted by shared category list not synchronized. Keep the first correction reversible.
Commit or escalate with evidence
Confirm: A new matching message receives the correct category and final filing. If that cannot be reproduced, restore the original safe configuration and send sanitized observations to the mailbox provider or authorized workspace administrator. Safety boundary: Do not export or reset a mailbox just for one category rule.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Assuming category assigned after rule evaluation is proven simply because the visible symptom matches this page.
- Changing multiple accounts, rules, connections or device settings before running the control: Compare message category at arrival versus after client processing.
- Skipping this safety boundary: Do not export or reset a mailbox just for one category rule.
- Resetting, formatting, deleting credentials or replacing hardware without a confirmed backup, a supported recovery path and evidence that the step is necessary.
A setting that makes one symptom disappear is not always the correct permanent configuration. If it disables another essential function, revert it and investigate the underlying dependency rather than leaving an unsafe workaround in place.
How to Verify the Fix
The primary pass condition is specific: A new matching message receives the correct category and final filing. Repeat the original workflow, not a loosely related shortcut, and confirm both the previously failing behavior and an unaffected comparison still work.
- Record the before-and-after state in the same location, account and operating mode.
- Repeat the original comparison: Compare message category at arrival versus after client processing.
- Check the stated pass result: A new matching message receives the correct category and final filing.
- Confirm that normal security, notification, storage or physical safety protections remain enabled.
If the result works only once or disappears after reopening the app, reconnecting the accessory or waiting for the next scheduled event, treat the issue as intermittent instead of fixed. Keep the event time and what changed between attempts.
If the Problem Continues
If the safe correction does not work, move to a focused deeper investigation: Review rule sequence and client dependency, using a mailbox-native condition if available. This is a different path from the first settings check; use it only if the device or service supports the required diagnostics.
When escalating to the mailbox provider or authorized workspace administrator, provide the exact symptom, result of the control test, changes already tried, time of occurrence and any non-sensitive error or status data. Explain whether category assigned after rule evaluation, client-side only action and shared category list not synchronized were supported or contradicted by evidence.
Do not share account recovery codes, private documents, live access tokens, sensitive location histories or full recordings merely to prove the problem. Redact or summarize identifiers before opening a public support request.
Prevent Recurrence
Keep a short reference note with the working configuration and the successful check: A new matching message receives the correct category and final filing. After an app update, firmware change, network migration or scheduled clock change, run the same short test before depending on the function again.
Watch for the condition that originally made the failure visible: Existing mail is categorized and searchable yet the category-based arrival rule does nothing. Where practical, retain an alternative approved way to perform the essential task so that one device, cloud service or interface does not become a single point of failure.
FAQ
How can I tell whether category assigned after rule evaluation is responsible?
Run the controlled comparison: Compare message category at arrival versus after client processing. A change that specifically affects the failing layer supports this hypothesis, but repeat it before changing permanent settings.
What if the real cause is client-side only action rather than category assigned after rule evaluation?
Do not repeat the initial correction blindly. Check the supported diagnostic path: Review rule sequence and client dependency, using a mailbox-native condition if available. Keep the earlier working configuration recorded so you can reverse the test.
When is this particular issue resolved?
The decisive result is: A new matching message receives the correct category and final filing. If it fails after the normal workflow is repeated, document whether shared category list not synchronized still explains the remaining behavior and escalate with non-sensitive observations.