Reporting content stuck in Submitted / Pending

Modified on Thu, 14 Aug at 7:37 PM

Content that is stuck in Submitted status will not be seen in the Compliance HQ. Often, it will initially display as Pending in a specific queue but will revert back and get stuck in Submitted. These items must be released back to a Draft status by the VDAOPS team.

Alternatively, content may also be stuck in a Pending status with no queue assigned to it (and rarely, it may look like a completely normal Pending submission). Identify the content where the issue is occurring and check if it may be edited and resubmitted. If not: a new ticket must be opened up in Jira to request the item be released.


Jira ticket

Project: VDAOPS

Work Type: Task

Ticket title: Client name: Revert submissions to draft state

Status: New Request

Description: 

Environment: (Name of environment)

Hub name: (Name of hub)

Advisor name: (Name of advisor to impersonate)

Freshdesk ticket: (if applicable)

Include list of items that need to be reverted.


  1. Once the content has been reverted, review it for anything that may have caused an issue. This can be code or special characters.

  2. Remove any potentially problematic code then resubmit the content.

  3. Let the reporter know that the content has been resubmitted and ask them to. Ensure that the content gets submitted and approved successfully before closing the ticket, as it may encounter a Submitted status issue again after review.

  4. Once you have confirmed that the issue has been resolved, you may close the ticket.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article