Workflow job failed to start
We are trying to run an Advanced Workflow that looks to see if a a values list contains certain values. If it does, it is suppose to apply a specific layout. We have the Advanced Workflow set to manual and every time I try and run it i get an error that says:
"Workflow Job Failed to Start"
According to the documentation it says the resolution is "Contact your RSA Archer Administrator"
We are on Archer 6.3 P1H1
Any help would be appreciated.
- Advanced Workflow
- archer 6.3
- Community Thread
- Forum Thread
- RSA Archer
- RSA Archer Suite
We're on 22.214.171.124 and I'm getting that error when a data feed tries to create a record in an application that uses AWF. I also get the error when creating a package with an application that has AWF. My Work Flow service is running; I can modify records and see them moving through the AWF nodes. Has anyone solved this?
We are on 6.3 P4, my data feed also having the same issue, as shown attached.
We resolved this by starting the RSA Archer Advance Workflow service in the service server, on top of running the service in the web server. As I understand this is not the recommended way for the service but it works, please let us know if there is a better solution.
Thank you, I've been beating my head against the wall for a week. I thought the issue was just in our newly created DEV environment (at 126.96.36.199), because it's fine in our 6.3.3 environments and our other 188.8.131.52 environment. I've been poring over the configuration. Once again, Archer Community to the rescue!
Update: I found another thread with another suggestion. Basically it says you should package and install the app in the same environment to fix it. Explanation is here: https://community.rsa.com/thread/190507. Unfortunately, I get the same error message when I try to package the application with AWF, so this won't work for me. I have a ticket in with RSA because our sys admin is hesitant to ignore RSA advice and install the service in two places.
Any other workarounds or suggestions welcome!
I know we resolved the issue but I can't find any notes on root cause. I believe it was a configuration issue related to our new environment.