Error The request queue is no longer available

[BillZ-123]

Hello

This is my second time creating a Help request queue. The first is working correctly and I referenced the first when creating the second. Currently the second is not appearing in the drop down on the requests page and when I use the direct link I get the following error "Error The request queue is no longer available". Any thoughts?

Thanks

Bill

[Daniel_Clarke]

Hi Bill! 

First thought would be, did you scroll down and "save" once you clicked the request queue checkbox? Unfortunately the system shows you all the goodies and even the link before it is truly active upon save!

Second thought would be, what were your sharing permissions set to in the "Who can add requests to this queue" area?

[NicholeVargas]

@BillZ-123 In order for a request queue to show up in the Requests area, the following 2 things must be in place:

• The project is set to Current (or status that equates with Current)
• The checkbox for "Publish as Help Request Queue" is selected under the Queue Details section 

If both of these are true and you are still not seeing the project in the Requests area, let us know! 

[PagidalaGu3]

Hi @BillZ-123 What is the resolution for this problem? Could someone please share the solution? I am encountering the same error across all environments. Is there a potential access issue? Any insights on this matter would be appreciated.

[MorganHatcher]

@PagidalaGu3 - a note that I am also having this problem right now too, might be a Workfront issue. 

[karinasaijo]

Same in my instances, just on some queue topics, and I couldn't find a pattern.

[MorganHatcher]

I thought it was just queues with topics included, since two without topics didn't have the error, but then those starting having issues too. I did submit a support ticket. 

[karinasaijo]

Found what it is, it seems like it's related to external look up field. I removed the one I had and the form worked. 

[MorganHatcher]

Good catch! I removed the form with the external lookup field too and the error is gone, will have the support team look into this.