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

Question

Question

Workflow Unexplained Missing Token

asked on June 17, 2015 Show version history

I have a find entry activity that finds the starting entry and returns the additional property Parent ID. This should create a token called FindEntry_OutputEntry_ParentID. The token shows in the token picker.

 

_________________________________________________________________________

 

When I run the workflow I get this message that the token does not exist.

 

 

When tracking and viewing tokens (organized by name) I can see that the token was never created as it should be. This only happens intermittently, how is this possible?

 

0 0

Replies

replied on June 18, 2015
 
 

Not 100% sure but this looks similar to token scope issue discussed over here.

 

Have you tried assigning the token generated by the find entry activity to a separate token with the assign token activity immediately after the find entry activity?

 

I believe the workflow profile running needs the rights to see additional properties as well, so that could be a source of inconsistent results.

 

Hope this can help,

Carl

 
0 0
replied on June 18, 2015

I am not sure how it could be out of scope. There are no conditions, loops, etc. This is just a linear set of two activities. I would be unable to assign the value to a token since the token I need to reference does not exist at all, see final screenshot showing all tokens.

0 0
replied on June 18, 2015

Ah I blurred your two images together as one. My apologies.

 

Tried to replicate the issue for a few minutes and couldn't :/

 

 

0 0
replied on June 18, 2015

Your screenshots only show a partial picture, so there's not enough information to troubleshoot. Carl might be right, but it's impossible to tell from the screenshots.

Something is definitely weird because your activities above the Try-catch branch and inside it have the same names and that shouldn't be allowed.

Side note, you don't need 2 activities to get the Parent Folder. Running Find Entry on the Entry Path token will accomplish the same thing.

0 0
replied on June 19, 2015

Those are two different screenshots of the same activities. I added a line between them for clarity. The try catch was added afterwards to prevent the workflow from failing due to a missing token.

0 0
replied on June 18, 2015

For clarity:

Your Find Entry activity intended to run on the workflow starting entry correct?

Do any of your activities change the Starting Entry?

What is the intended purpose of the Search Repository activity?

0 0
replied on June 19, 2015

The find entry runs on the starting entry which is never changed. The search repository is not used as part of this process, it is for another purpose. These two processes exist independent of anything else in the workflow. They are simply there to get the parent folder of the starting entry. It works most of the time, it just didn't work for a couple days. How is it possible that token was missing for only a couple days?

0 0
replied on May 2, 2018

Hello all,

I am running into this same issue. We have a workflow that is failing in the exact same way. Yet when I re-run it, it works fine. This is no small endeavor though as it is part of a fairly complex workflow that requires multiple steps to re-run.

 

The only thing I can guess is that we had to re-publish this workflow updating existing instances. Even though it seemed to take fine, we've had this side effect along with steps re-running unexpectedly (not in a loop or anything). The only update we made for the new version was to on one step... not changing the flow or related tokens.

 

I'm wondering if perhaps this is a known issue in certain circumstances. We are running workflow 10.2

 

Thanks,

Julie

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

Sign in to reply to this post.