Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Dynamics 365 general forum

Removing a workflow from a BPF stage exit

(0) ShareShare
ReportReport
Posted on by

Hi,

Dynamics 365 v9 (latest update). I have 3 async on demand workflows firing on stage exit of a stage in a BPF. I have been experiencing intermittent behaviour with the firing multiple times (sometimes over 15 times!). I saw a previous blog post on this and it seemed to relate to the number of saves done to the BPF, almost like it was storing up a version history of them and firing every one of them. Anyway, that behaviour seemed to calm down so I left it. It has returned however, and rather than fight it, I just wanted to remove the workflows and have them triggered in a different way. I removed workflow 1 from the BPF, amended it to be not on demand, triggered on the field I am interested in, however now the BPF will not function and complains the workflow is not on demand. So it is still trying to call it even though it is removed entirely from the BPF. Even more worrying, it is trying to call workflows I have moved to different stages some time ago!

I know I could nuke the BPF and create another one, but since they became their own entity this is a non trivial exercise with data already in production in use.

Anybody seen this before and know any resolution? I have logged a ticket with MS in the meantime.

Thanks,

Nick

  • Community Member Profile Picture
    on at
    RE: Removing a workflow from a BPF stage exit

    Replicated with a vanilla BPF and basic workflow on a call with Microsoft. Attach a new workflow to stage exit and update a field, watch it update the field (with a noticeable degradation in performance on stage change....). Remove workflow from stage exit (or entrance for that matter) on the BPF, workflow logic still fires, field still updates even thought workflow no longer associated to BPF. Bottom line, I would steer clear of using them at the moment and instead hook onto stage changes on the BPF entity itself, that is much more performant and reliable (and async wflows actually run async)....the only workaround I have at the moment is to create the BPF from scratch (d'oh) and never associate any workflows in the first place.....

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

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,865 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,723 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156 Moderator

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans