Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested answer

Assistance Needed with Workflow Errors in Dynamics

(0) ShareShare
ReportReport
Posted on by 12

Dear Microsoft Support Team,

 I am encountering an issue with Dynamics where workflows are reporting an error stating that the record does not exist. The original intention was for the workflow to only initiate in the background when an email with a reference to the /Account/ entity is created. However, the workflow is also triggered when an email with a reference to the /Lead/ entity is created.

The primary issue arises when this error occurs. Instead of aborting the workflow, Dynamics sets the workflow to /Wait until 9999./ My question is, is it possible to delete these system jobs weekly with a bulk delete job? Will they persist after deletion, or do I need to manually cancel them beforehand?

Your assistance in resolving this matter would be greatly appreciated.

Thank you in advance.

  • Suggested answer
    RudyZhang Profile Picture
    Microsoft Employee on at
    Assistance Needed with Workflow Errors in Dynamics
    Hi,
     
    We have analyzed your requirements, and you can try to delete these system jobs weekly using Bulk Delete Jobs in Dynamics 365, here are some simple steps.
    1. Go to /Settings -> Data Management/

    2. Select /Bulk Record Deletion/

    3. Click /New/ and the Bulk Deletion Wizard will appear.

    You can also use Bulk Delete Manager
    Please refer to the following link
    https://www.xrmtoolbox.com/plugins/CrmGustaf.XTB.BulkDeleteManager/
     
    In addition, you may need to manually cancel these system jobs before deletion to avoid data loss. The minimum recurrence frequency for batch delete jobs is 7 days. To schedule daily bulk delete jobs, you can schedule multiple bulk delete jobs, one for each day of the week. Set each job to repeat every 7 days.

    As for workflows being triggered incorrectly, you may need to check the conditions that are set up to trigger the workflow. Make sure the workflow is only set to trigger the /Account/ entity and not the /Lead/ entity.
     
     
    I hope my answer is helpful to you! If you have any other questions, please feel free to contact me.
     
    Best Regards,
    Rudy Zhang

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Jainam Kothari – Community Spotlight

We are honored to recognize Jainam Kothari as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Daivat Vartak (v-9davar) Profile Picture

Daivat Vartak (v-9d... 671 Super User 2025 Season 1

#2
Vahid Ghafarpour Profile Picture

Vahid Ghafarpour 167 Super User 2025 Season 1

#3
Muhammad Shahzad Shafique Profile Picture

Muhammad Shahzad Sh... 138 Most Valuable Professional

Product updates

Dynamics 365 release plans