NVIDIA Inception Portal Glitch - Benefit State Reset Request

Community Information Forum Feedback
1

Hi NVIDIA Community & DevRel Team,

Posting here as an escalation following unhandled emails to inceptionprogram@nvidia.com.

Our startup, Crystal Prism Software, is an active NVIDIA Inception member.
We attempted to apply for the AWS Cloud Credits benefit through the Inception portal, but encountered a form issue where the intake submission locked prematurely before entry was completed.

Current Stat

  1. The Inception portal benefit button is permanently locked/greyed out in a “Submitted” state.
    (Note: The button state was previously reset once by support, but the intake token/backend state remained stuck and immediately glitched back).
  2. AWS Activate Support confirmed directly that they never received a valid application payload and instructed us to have NVIDIA clear our submission state so we can re-apply.
  3. Multiple follow-ups to inceptionprogram@nvidia.com over the past month have gone unanswered, and our account manager now has become unresponsive to.

Could an NVIDIA team member or forum moderator please escalate this to the Inception portal operations team to perform a manual state reset for Crystal Prism Software?

Thank you,
Oleg Volkovinski
Founder, Crystal Prism Software

4

Hi @oleg.volkovinski

The team has replied to you via email, your benefit has been reset so you can submit a new request.

5

Hi Tom,

Thank you so much for the swift help!

The reset worked - I was able to complete the intake form and successfully submit the application on the AWS side.

Just as a quick heads-up: there appears to be an active trigger issue with the portal form.
It sends out a “submission confirmed” email while a user is still actively typing in the input fields (before hitting submit), which is what caused the premature lockout originally.

Really appreciate your assistance in getting this resolved!

Best regards,

6

Thanks for the heads-up!

7

Thanks @lucasblake686! Spot on - Tom from the NVIDIA team was able to escalate it and get the backend state reset today.