cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
266
Views
0
Helpful
4
Replies
Highlighted
Beginner

Workflows not working after Renaming Resource

We sync AD to CUCM and recently removed uppercase characters from some usernames in AD and resynced to CCX. After the rename, workflows do not run for agents. After renaming the agents, I did have to place them back in the correct team and reassign skills and readd permissions in CUCM.

When I go to http://fqdn/finesse/api/User/username/Workflows it is blank.

The same workflows are working fine for other users in the Team that were not renamed.

 

I'm a bit at a loss as to what to check and how to get the workflows running again.

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Beginner

Re: Workflows not working after Renaming Resource

I may have been overthinking this issue a bit. I ended up removing the agents from the Team and re-added them. Workflows are now executing properly.

View solution in original post

4 REPLIES 4
Highlighted
Participant

Re: Workflows not working after Renaming Resource

...just a quick thought: try logging out one of the updated agent IDs.
Verify the Agent ID and Team association are updated in Finesse Admin. ...they may have to logout and then log back in, to receive the update/changes to the Workflow/Finesse.
Hope this helps.
-Sean
Highlighted
Beginner

Re: Workflows not working after Renaming Resource


@Sean Lynch wrote:
...just a quick thought: try logging out one of the updated agent IDs.
Verify the Agent ID and Team association are updated in Finesse Admin. ...they may have to logout and then log back in, to receive the update/changes to the Workflow/Finesse.
Hope this helps.
-Sean

Thanks, we actually tried that a few times.

Highlighted
Participant

Re: Workflows not working after Renaming Resource

....all good. Glad you got it working.
-Sean
Highlighted
Beginner

Re: Workflows not working after Renaming Resource

I may have been overthinking this issue a bit. I ended up removing the agents from the Team and re-added them. Workflows are now executing properly.

View solution in original post