Jump to content

Delay in AutoTask workflow being available for use after publishing?


Recommended Posts

Posted

In My Change Request workflow I successfully used the nodes to create Teams Conversations for a few months now. Occasionally one fails so I want an AutoTask to create one Manually. Using the same Channel ID and Team Group ID as I do in the CR workflow itself, when I run the Autotask, I got this error:

image.png.d0fc90923b19b93b36a77919d8317826.png or this error:

image.png.6e9ecb1809e8ed753d9b7820bdf1a5b6.png

And that depends on which of the options I select in this:

image.png.3913b2a563f62af8ec823b69146da4ca.png

At first I thought there was a config error so I tried again and again. And now, 10 minutes later, it just works.

Is there a cheeky delay in the AutoTask workflow sorting-out it's permissions in the back-end so it's not ready for short while? I think I've seen this before.

  • Berto2002 changed the title to Delay in AutoTask workflow being available for use after publishing?
Posted

No "cheeky delay" that I'm aware of.  At least, not on the Hornbill side.  It is always possibly that something is happening on the Teams side.  If the Auto Task is running from a request, then the For Entity will need to be set to Requests.  

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...