Warewolf Refresh workflow (FetchExplorerItemsService.json) is getting hang when calling from pipeline

Anonymous 2 months ago 0

Hello , 

Warewolf Server Configuration 

Warewolf version -

Workflow - 1200 

CPU(s) - 16 cores 

RAM - 64 GB 

we are deploying Warewolf server using azure pipeline. the command we are using to refresh workflow is 

powershell -ExecutionPolicy Bypass -Command "Invoke-WebRequest http://localhost:3142/services/FetchExplorerItemsService.json?ReloadResourceCatalogue=true -UseBasicParsing -UseDefaultCredentials"

Image 1110

as you can see in above screenshot , it is hang up there by 1 hours , in most case it should be finish by 10 secs. 

could you please support us to fix this problem ? 

deploy workflow

how to find the value of a variable in Activity Designer

Anonymous 4 months ago 0

anyone tell me?

Under review

While Unit test run why need to connect actual resources

bhavesh panchal 10 months ago updated by Ashley Lewis 8 months ago 1

We have identified that if we are not using actual values for DB and other resources for workflows it fails Unit tests.

It causes issue while unit test run when unit test container connects to actual DB and other resources, there might be chances of Data manipulation at Unit test level.


Warewolf swagger support for API documentation

Anonymous 10 months ago updated by anonymous 10 months ago 1

Warewolf needs API Documentation tool like swagger. 

currently we have to preprare API documentation manually and maintain manually whenever  there is anykind of update in APIs.

it is very tedious process to do so. 


Handeling of Errors

bbuchan 12 months ago 0

Given A nested workflow has an error

Or Given a tool has an error

And given the error is handled in On Error section of tool

When returning a result

Then the result should be present

execution tool variables

Group to new workflow

Anonymous 1 year ago 0


I have a feature suggestion. 


Sometimes a developer will create a workflow and then realise that a portion of the workflow could be made into a sub-workflow.

Current State: 

1. Developer would open a new workflow and copy the code there and save.

2. Developer would then move the new workflow from explorer to their main workflow and wire up the new item.

Desired State:

1. Developer highlights the tools that they want to move, including their connections.

2. Developer right clicks any of the tools and selects create new workflow.

3. A new workflow is created and wired the same as the current workflow.

4. Developer will review the new workflow and save the new workflow. 

5. Developer wires the new workflow in the main workflow.


1. Developers need tools (IDE/Studio) to speed up development.

2. This feature will promote component reusability and simplify the main workflow for readability. 

designer studio tool workflow
Under review

hi i am new to this tool, i just want to create an array of numbers

Anonymous 1 year ago updated by Gandalf 1 year ago 1

hi i am new to this tool, i just want to create an array of numbers


Service/Workflow not showing on my folder structure

Siya 1 year ago 0

Good Day,

After creating a workflow/service on Warewolf I can not see it on the folder structutre “C:\ProgramData\Warewolf\Resources” Please assist.




Face issue while creating Unit test cases with Select and apply tools on WW version 2.7.5

Anonymous 1 year ago 0

Hi Team,

i'm using WW version 2.7.5

I tried to create a test cases and there were issue was facing when I have used Select and apply with sequence tool.

I have attached the video link for more understanding.


Not a bug

Facing Service Unavailable issue with Warewolf version

Anonymous 2 years ago updated by Siphamandla Dube 2 years ago 2

I have already tried below Scenarios


1) Uninstall warewolf existing version

2) Remove Warewolf files from (ProgramData, ProgramFiles (x86), App Data)

3) Restart the system

4) install the warewolf version


1) Install .Net Framework 4.8 

2) Uninstall warewolf existing version

3) Remove Warewolf files from (ProgramData, ProgramFiles (x86), App Data)

4) Restart the system

5) install the warewolf version


1) Update my windows

2) Uninstall warewolf existing version

3) Remove Warewolf files from (ProgramData, ProgramFiles (x86), App Data)

4) Restart the system

5) install the warewolf version


1) Perform the Repair for the warewolf version


1) Restart the Warewolf Service


1) Install the new version of Warewolf 2.7.1 & Still facing the same issue 

Please find attachment here for server logs.