When using Quest On Demand Migration's Email Rewrite / Domain Rewrite feature, the Enable Rewrite action may complete successfully and correctly transition users to the "Enabled Rewrite" state, but the Job History section for these users displays as empty and Download Job Logs returns no results. This is expected product behavior when the Skip Mail Forwarding option is selected during the Enable Rewrite operation — the user is transitioned to the new state without a forwarding-configuration job being executed, and therefore no Job History entry is created. This article documents the symptom, the cause, and confirmation that no action is required.
Symptoms reported on an affected On Demand Migration project:
Last Updated timestamp on the affected user records matches the time the Enable Rewrite operation was executed, confirming that the action did run and did transition the user state — it is only the Job History record that is absent.This is expected product behavior, not a defect. No corrective action is required.
When the Enable Rewrite action is executed with the Skip Mail Forwarding option selected, the On Demand Migration Domain Rewrite workflow performs only the state transition for the affected users. Because the mail-forwarding configuration step is explicitly skipped, there is no underlying job operation to record, and consequently no Job History entry is created and no Job History is displayed in the UI.
Job History entries are generated only when a Domain Rewrite / Email Rewrite action actually executes a job — for example, the "Prepare User for Address Rewrite" action, or an Enable Rewrite performed without Skip Mail Forwarding, where forwarding is actively configured. A pure state transition with no downstream work to perform does not produce a Job History entry, by design.