You are viewing limited content. For full access, please sign in.

Question

Question

Laserfiche Workflow 12 – Search Repository activity remains stuck in Running

asked one day ago

Title: Laserfiche Workflow 12 – Search Repository activity remains stuck in Running

Hello,

I am experiencing an issue with Laserfiche Workflow 12 (version 12.0.2605.385).

When I execute a workflow containing the Search Repository activity, the activity remains in Running or Task Executing status and never proceeds to the next step.

The search query works correctly when tested in Workflow Designer and returns the expected results. However, during actual workflow execution, it gets stuck.

I have already checked the Workflow services, server connectivity, SQL connectivity, and available logs, but I have not found any errors explaining the issue.

The repository is hosted in AWS, while Workflow is installed on a local server.

Has anyone experienced this behavior or knows what could cause the Search Repository activity to remain running even when the query works correctly in Designer?

Any suggestions or guidance would be greatly appreciated.

Thank you!

0 0

Replies

replied one day ago

 1. In the Workflow Administration Console, go to Advanced Diagnostics > Tasks and look at the running Search tasks while the issue is present. Note their start time, status, action, and next retry time. Also check whether all Search Repository activities are affected or only this workflow, and whether other activities (e.g. Find Entries) still run normally.
 2. Look at the network path between the Workflow server and the AWS-hosted Laserfiche Server: firewalls/NAT devices that drop idle or long-lived connections, proxies, and latency. Try to test Workflow Designer on the Workflow Server.
 3. Check the Workflow service account and the connection settings:
   - Is the Workflow service running as Local System? Try running the service under a domain account as a test.
   - As a diagnostic, try toggling the TLS option on the connection profile and re-running.

If this is not caused by a network or profile configuration issue, please contact Laserfiche Support to open a support case and provide the screenshots of the running tasks, along with package captures (e.g., Wireshark traces) collected for WF Server and LF server when reproducing the issue by triggering the workflow with that activity. We'll look into that issue further there.

Thanks

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.