workflow worked but terminated

asked on June 5, 2019 • Show version history

This workflow is meant to bundle "case folders" with matching template/ client name (fields/ token)/ case number (field/token) and move existing case folders within a newly created case folder.

This is actually working in the web client! The case folders actually move to the newly created case folder just like it should... But when I look at the workflow history, it shows the workflow terminated due to Access Error

We verified the connection profile of WF DOES have access granted, so not sure why this is happening. Checked the rights on Admin Console and they have all those too.

What it should be doing.PNG (155.29 KB)

| Download

Workflow ran.PNG (20.67 KB)

| Download

Error messages.PNG (19.41 KB)

| Download

0 0

replied on June 6, 2019

What user are you using for the Workflow? Does that user have access rights to move the file?

0 0

View 1 previous reply

replied on June 6, 2019

We're using a WF user for the workflow, we've double checked it has all the Admin Console rights and privileges and double checked volume rights and repository rights- so all the access is there and the funny part is, the entry actually moves!

So that is what confuses me- It says access denied but the entry still moves... BUT- I did find this today: When I look at the terminated workflow details, and I look at Entries, it wants me to login to see the entries and then it pulls up the thick client repo on the server and gives me the same access denied error code! What does the entry tab mean in workflow designer? Why would it get connected to the thick client on the server? I'm attaching screen shots so you can see. Thank you!

What does entries mean.PNG (63.82 KB)

| Download

What is this.PNG (128.8 KB)

| Download

0 0

replied on June 6, 2019

There should be a more detailed error message in the WF Admin Console under Monitoring\Error Logs\activity errors.log

Entry Details pane will try to log in as the user logged into the machine running the Designer when you select Windows authentication. It doesn't have any relation to the error you saw in the Messages tab.

0 0

replied on June 7, 2019

Thank you, I was hoping for some more info around the error! I'm attaching the details I found, but I don't know what they mean :/

Error log.PNG (75.24 KB)

| Download

0 0

replied on June 8, 2019

Inside of the For Each loop, before the Move Entry activity, add a Create Token Values activity and create a token with the Move To path in it and then add a Track Tokens activity and track the Move To token value. Then run the workflow and see if each time the For Each Entry runs if it is create the path that you expect.

2 0

Question

Question

Replies

Sign in to reply to this post.