nikivi Posted October 9, 2019 Share Posted October 9, 2019 (edited) Got this issue on my workflow. I am not on v10.15 but users of my workflows and I suppose others too will get this prompt on calling an external trigger or keyword. What should they do to get around it? I found this issue online when googling for error. Is there anything @Andrew and Alfred can do to remove this friction? Edited October 9, 2019 by nikivi Link to comment Share on other sites More sharing options...
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
Already have an account? Sign in here.Sign In Now