Skip to content

Fix expired unlock challenges returning 500 - #556

Merged
barry01-hash merged 4 commits into
PromptMintLabs:mainfrom
Marvelg256:fix/508-unlock-expired-challenge-401
Sep 3, 2026
Merged

Fix expired unlock challenges returning 500#556
barry01-hash merged 4 commits into
PromptMintLabs:mainfrom
Marvelg256:fix/508-unlock-expired-challenge-401

Conversation

@Marvelg256

Copy link
Copy Markdown
Contributor

Summary

  • Return HTTP 401 when an unlock challenge token has expired.
  • Provide a clear message instructing users to request a new challenge.
  • Apply the behavior to prompt and bundle unlock endpoints.
  • Add a regression test covering expired challenge tokens.

Testing

  • yarn.cmd vitest run api/prompts/repro-expired-token.test.ts --reporter=verbose
  • Test result: 1 passed

Related issue

Closes #508

Marvelg256 and others added 3 commits August 30, 2026 16:24
Update both prompt and bundle unlock endpoints to return a 401 status code
with a clear message when a challenge token is expired, instead of 500.

close PromptMintLabs#508
@drips-wave

drips-wave Bot commented Aug 30, 2026

Copy link
Copy Markdown

@Marvelg256 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@barry01-hash
barry01-hash merged commit aaade55 into PromptMintLabs:main Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix: unlock returns 500 on expired challenge instead of 401

2 participants