Advanced Workflow Verification

Verify that the advanced workflow feature installation was successful. This involves checking cache settings, and resolving installation issues.

Important: If you do not have access to the server on which the Advanced Workflow service is installed, contact your system administrator.

On this page

General Advanced Workflow installation issues

 
Issue Troubleshooting

Records enrolled in Advanced Workflow fail to transition from Evaluate Content nodes.

This issue may occur if you stop the Advanced Workflow service during the content enrollment process. When you start the Advanced Workflow service again, any Evaluate Content nodes that experienced this issue within the previous 90 days are reset.

For example, when you start the Advanced Workflow service again, any Evaluate Content nodes that experienced this issue between January 4, 2023 and the current date of April 4, 2023, are reset.

Application Request Routing cache settings for Advanced Workflow

Review the Application Request Routing cache settings that populate in IIS, in a new installation.

The following table describes the suggested values for each field.
Field Value

Enable Proxy

Selected

HTTP Version

Pass through

Keep alive

Selected

Time-out (seconds)

120

Reverse rewrite host in response headers

Selected

Preserve client IP in the following header

X-Forwarded-For

Include TCP port from Client IP

Selected

Memory Cache duration (seconds)

60

Enable disk cache

Selected

Query string support

Ignore query string

Troubleshooting installation issues

Use the following process to troubleshoot the Advanced Workflow service if you cannot access the advanced workflow functionality in Application Builder or your test workflow fails.

Important: If you do not have access to the server on which the Advanced Workflow service is installed, contact your system administrator.

The following table describes the troubleshooting process.

Step

Question to answer

How to find out

Result

Action

1

Can Microsoft Internet Information Services (IIS) communicate with the Advanced Workflow service?
  1. Log in to Archer.
  2. From the menu, click Admin menu.
  3. Under Advanced Workflow, select Job Troubleshooting.

 

If the page loads, the test passed.

Go to step 2 in this table to confirm that the Advanced Workflow service is running.

 

 

 

If the page does not load or renders an error page, the test failed.

Go to Troubleshoot communication between IIS and the Advanced Workflow service.

2

Is the Advanced Workflow service running?

Open the Windows service Control Manager and see if the Advanced Workflow service is running.

The service is running.

Go to Troubleshoot the Advanced Workflow application server deployment.

The service exists, but is not running.

Start the service.

The service does not exist.

Go to Troubleshoot the Advanced Workflow service.

Troubleshooting options

Communication between IIS and the Advanced Workflow service

  1. Open IIS Manager. At the global server level, if the Application Request Routing module does not exist, do the following:
    1. Reboot your system. See if the module now exists.
    2. If 1a does not work, repeat the installation. On the Installation Options page, verify that only Advanced Workflow Service is selected.
  2. Open the Application Request Routing module.
  3. In the Cache Setting section, verify that Enable Disk Cache is selected and click Apply.
  4. In IIS, verify that the WebDAV feature is disabled for your Archer site. Archer does not support the WebDAV feature.
  5. Open the Archer Control Panel. Navigate to the Install Settings page and the Advanced Workflow frame. Ensure that the Workflow Host or Load Balancer URL match the values used for Advanced Workflow REST URL and Advanced Workflow Communication Port during the installation process.
  6. If you are encrypting advanced workflow, verify that a dedicated certificate was imported properly into the local machine's personal store. See Preparing Encryption for Advanced Workflow for more information.

Advanced Workflow Service

  1. Verify that the installer created the Advanced Workflow service:

    C:\Program Files\Archer\Services\ArcherTech.Services.WorkflowService.exe

  2. Verify that the installer created the following directory:

    C:\Program Files\Archer\Services\Workpoint

  3. If the installer did not create either or both of the above, repeat the installation.

Advanced Workflow application server deployment

  1. In the Task Manager, verify that the following are running:
    • WpAsyncMonitor.exe
    • WpEventMonitor.exe
    • WpGeneralMonitor.exe
    • WpJobMonitor.exe
    • WpServiceHost.exe
  2. Check the service wrapper log file for errors in the file C:\ArcherFiles\Logging\Archer.ArcherTech.Services.WorkflowService.date.xml.
  3. If you have enabled logging in the Archer Control Panel, open C:\ArcherFiles\Logging and check if the ArcherAdvancedWorkflow.xml file exists. If the file does not exist, contact Archer support.

Note: C:\ArcherFiles is a configurable field in the Archer Control Panel. For more information, see the Archer Control Panel Help.

High-availability or load-balanced environments

While using a high-availability or load-balanced environment, if 1 of the servers running advanced workflow fails, all calls in progress are interrupted and rerouted to another available host. In addition, new calls go through the new host. This protects users.

Data feed failures

If failures occur while running data feeds, review the data logs for any lost information. View the data feed results log, Archer.ArcherTech.DataFeed.log, in the directory set during installation.

Job Framework response time

Sometimes the Job Framework response time is too fast for the load balancer. To extend the response time, alter the ArcherTech.JobFramework.exe.config or web.config files, according to the errors listed in the following chart:

The following table describes the errors and their settings.
Error Encountered

Setting

Description

Advanced workflow HTTP request error, attempt X. The operation will be retried in X milliseconds.

wpRetryAttemptsOnFailure

The number of times to retry a failed connection to the Workpoint API before stopping (the default is 5).

Advanced workflow HTTP request error.

wpRetryDelayMillisec

The number of milliseconds to wait between attempts at API calls to Workpoint (the default is 2000).