Using queue method - severe guardrail warning

We have activity and have step which calling Queue method (not queue-for-agent) with another activity to run in asynchronously (please find the attached screenshots). One thing we are considering to convert this to queue-for-agent but need lot of testing.

Just started upgrading the application from V7.1.5 to V7.4 and started seeing following new severe warning. I would be grateful if anyone see similar issue and solution.

Guardrail wanring - Functionality: Severe

When using the Queue instruction, the queued activity will not be run on the primary or step page specified. Check the Help documentation for more information.


Keep up to date on this post and subscribe to comments

April 22, 2019 - 9:21am

I am still waiting for help.

July 15, 2019 - 3:56pm

This warning is a very useful one, because it is quite unusual for there to be no step or primary page when the activity fires.  This can lead to a difficult to debug issue if your calling activity is relying on there being a step page or primary page.  As the warning says, THERE WILL BE NONE.

You can add a "justification" for the warning, and I believe the score will not be added to your total guardrail score.