We've met the following criteria and we're thinking that this is a platform bug because what we're seeing in the go-live dashboard isn't reflecting the "declined" state that's indicated in Go-Live process documentation. We have a status of “Ready to submit” but received decline email. We have the IAM Standard subscription. 

Here are the criteria we're meeting:
- We have, and are submitting this request from, a dev sandbox account and integration key
- 20 or more successful API calls in a 24 hour period
- Integration exclusively using OAuth 2.0 for authentication
- Active production account with a plan activated (this account)
- Admin privileges on both the dev and prod accounts
- Review submitted via the actions -> go live process
- Logs are clean
- We’re thousands of calls below the rate limits
- The go-live request attached to this message is the one that's been declined twice

We’re not getting anything in the dev dashboard indicating a declined state, only that it’s ready to submit, even after both rejections. there’s also nothing in the production dashboard indicating that we’ve even started the process or anything. that’s part of the reason I’m thinking something might be goofed on the docusign side and wanted to check with support on it.



The rejection email that we're getting has the following content:

Declined: DocuSign API - Go Live Form
Matt King declined to sign.
Docusign API Team
go-live@docusign.com

Matt King declined Go-Live Form.docx, Go-Live Confirmation.pdf. As a result, the documents cannot be completed.
And when clicking the "review documents" link in the rejection email, we're getting the following message:

Envelope or Account Activation Not Found
The envelope is not accessible at this time.
The envelope may have been recalled by the sender or require additional processing.
Additionally, the recipient may have failed authentication.

For assistance, please visit our Support Center.

When entering the support code from the email to view the same documents with this key, "A0252B0C8197489D97F7B4E411284B7A1", we get the same message as above.

Please advise, as we're not getting any info in the dev dashboard, prod dashboard, or rejection messages about why this is happening.

We reached out to Support who simply told us to review resources or go to this Community Forum. Please help.