Data Mask does not reactivate Automations after experiencing a Fatal Error
Last updated 9 days ago ·Reference W-9061787 ·Reported By 3 users
In Review
Summary
If Data Mask experiences a fatal error causing processing to abort, the Data Mask process does not reactivate automations that were deactivated during the initial phase of the masking process.
Repro
None
Workaround
Workaround 1:
- After a fatal error is experienced and Configuration Status will show “Aborted“
- On the Configuration List View, click the down arrow for the configuration that experienced the fatal error.
- Click “Re-enable Automation”
* This must be done BEFORE kicking off a new execution. If another configuration is run before reactivating, follow steps in Workaround 2.
* Check Run Logs for the Automation Reactivation Complete log.
Workaround 2:
- In the case where the config was re-run before automation was re-enabled
- In the Run Logs, click a run log associated with the affected execution and and copy the Execution Id value.
- Go to Setup -> Custom Settings-> Masking Configuration -> Manage -> Edit-> Paste in the execution Id value from step 1 into the Current Execution ID field. Save
- Go back to the List View in data mask and select “Re-enable Automation” for that config
Reported By (3)
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.
