web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

New workflow versions causing existing instances to stop and batch job to error

(0) ShareShare
ReportReport
Posted on by

We've recently gone live with Dynamics AX 2012 and have identified changes and fixes required for some of our workflows.

 When I import my latest workflow xml file from one environment to another I have to de-activate the current version and activate and make default the new workflow ID and version.

This seems to stop the currently running workflow instances and the "Workflow message processing" batch job returns the error "failed to find workflow".

I can only resume things by recalling any pending workflow instances which are using the old version and resubmitting them which uses the updated version.

Is this a known issue, or do we likely have a separate issue in our test environment?

It would seem strange to have restart all pending workflow instances whenever you want to make even the simplest of updates.

Any thoughts on this or assistance would be much appreciated, thanks.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Sohaib Cheema Profile Picture
    49,668 Super User 2026 Season 1 on at

    when you resubmit a workflow it takes same old configuration.

    you can see this in resumeWorkflow (method) of Workflow(Class)

    your previous configuration should be active for old workflows

  • Sohaib Cheema Profile Picture
    49,668 Super User 2026 Season 1 on at

    sorry. I mean to say when you resume a workflow it takes old configuration id. Ignore word 'resubmit' in previous reply. consider it as 'resume'

  • Community Member Profile Picture
    on at

    Thanks for the reply Sohaib.

    I re-tested on a different AX environment, and I can indeed carry on completing tasks on an un old workflow version whilst having imported and activated a new workflow ID.

    So I expect the issues with the batch job are unique to that environment and making it look like the issue is to do with old workflow versions. I expect the actual issue is else where.

  • Sohaib Cheema Profile Picture
    49,668 Super User 2026 Season 1 on at

    Hi aron,

    what do you meant by 'un old workflow version '???

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

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 16

#2
Nagendra Varma K Profile Picture

Nagendra Varma K 4

#2
Harisgillani Profile Picture

Harisgillani 4

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans