
When an Imagild password-reset code does not arrive or is rejected, first check the email address, the operation that requested the code and whether you are using the latest relevant message. A registration code and a password-reset code are not interchangeable. Keep the recovery attempt focused on the existing account instead of repeatedly switching forms or creating another account.
Key Takeaways
- Check delivery and code acceptance as separate problems.
- Use the code requested from Set / forgot password?, with the same account email.
- A generic code-request acknowledgement does not confirm that an account exists.
- Stop guessing and contact support when the account or delivery state remains uncertain.
Decide which step actually failed
Identify the last confirmed event before requesting anything else. Did the website accept the request? Did the email arrive? Did you enter a code? Did the password save? These are separate checkpoints, so a problem at one step does not establish that the others failed.
| Observation | Check first | Avoid |
|---|---|---|
| No email is visible | Account email, inbox search and spam folder | Registering another account to recover the first |
| Several code messages arrived | The latest message for password recovery | Trying every old code in sequence |
| A code is rejected | Correct flow, same email, complete code | Repeated guesses |
| Password saved, but login fails | New password and normal sign-in screen | Continuing to enter a one-time code as the password |
Write down the visible outcome in your own words. A note such as “the code arrived, but saving the new password returned an error” is more useful than “login is broken.” Do not include the code itself in that note if it will be shared.
If the email has not arrived
Check the email typed into the recovery screen against the address used for the existing Imagild account. Look for a spelling error or a different personal or work address. A browser's selected Google profile does not establish which email you submitted to this form.
Search the inbox and spam folder for the recent message, including its time and purpose. If you use a managed mailbox, its normal filtering or delivery controls may also need attention. Do not disable account security or forward the whole mailbox to solve a single missing message.
Imagild's acknowledgement is deliberately conditional: if the address has an account, a code has been sent. Treat that message as a request acknowledgement, not proof that the email owns an account. OWASP's password-recovery guidance recommends consistent responses so recovery forms do not reveal which addresses are registered.
If you request another code through the visible control, wait for the corresponding latest message. Repeated requests can leave several messages in the inbox and make identification harder. An old message arriving late is still an old message.
If the code arrives but is rejected
Return to the password-setting flow reached through Set / forgot password?. Confirm that the email in that flow matches the destination of the message. Use the complete code without adding text from the email around it.
A code requested for registration should not be used to reset an existing password. A newer password-reset request also replaces the previous usable request. Codes are temporary and single-use, so a successfully consumed code is not a reusable login credential. Do not keep testing old codes after the password has already been saved.
If the screen reports that the two new passwords do not match, correct those fields rather than treating the message as an email-delivery problem. Once the password-save confirmation appears, follow the instruction to sign in with the new password.
A hypothetical mixed-message problem
Imagine requesting a registration code, then realizing you already have an account and opening password recovery. Two emails may now appear. The relevant message is the one for the current password-recovery request, not whichever email is easiest to find. If you request another reset code, use that newer reset message.
This example illustrates purpose and sequence; it is not an observed customer incident. It does not establish a universal email-delivery time or a guarantee that support can recover access without verifying account ownership.
Prepare a safe support request
If one deliberate attempt still leaves the outcome unclear, use Imagild support. Provide the account email through the private support channel, the approximate request time and time zone, the screen used and the exact visible error with secrets removed. State whether the message never arrived or arrived but was rejected.
Do not send passwords, one-time codes, API keys or unrelated private photos. If an existing job is involved, its identifier can help distinguish an account-access problem from a processing issue. The task recovery guide and pending-job guide cover that separate investigation.
Sources and scope
Checked October 30, 2026 against Imagild's password-recovery interface and implementation, with OWASP used only for the explanation of conditional acknowledgements. No email-delivery test, real password change or inbox inspection was performed. Restoring access does not create another welcome allowance; see the points guide.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. Report a correction.
Cover: AI-generated conceptual illustration; not an application screenshot, observed result, private account record or privacy guarantee.