Workflow and ServiceDesk Community

I'm using some Global Variables from Process Manager in my processes. My processes seem to have stopped working and they are failing on the components that reference the Global Variables.

Does anyone know what would cause Workflow to lose it's connection to Process Manager variables?

Thanks!

The properties.config file in a published WF directory typically holds the values of any project properties you define for a flow. I'd take a look at that file first and see if they match up.

Thanks reecardo but it's not an issue with the Project Properties, it's an issue with the variables in the Process Manager. These are set at a server level and are referenced whenever a project is run. That way if for example your company Mail Server changes you only have to change it in the Process Manager and not in every projects email components.

Phil

Phil, I've seen this recently.

In my case it seemed to be linked to a network outage.  The odd thing was the outage was only for an hour or two but it took hours longer for the workflows to recover (on their own) and be able to retrieve variables from the Process Manager.  It has made me shy away from using PM based variables even though they are perfect for information that is shared by many workflows.  I have been using OS based environment variables as a workable alternative.  Not so good if you're running a clustered setup though.

Sounds like something an iisreset and/or workflow services restart may help.  I wonder as well if auto-initialize is enabled on the affected workflows; I believe that option is intended to assist recovery from problems like that, but I may be mistaken.

Mine was an auto start workflow and yes auto-initialise was enabled.