Marketplace receipt handling errors

For the past few weeks one specific user in our experience can’t receive anything they buy. Their developer product purchases charge normally, but our ProcessReceipt callback is never called for them. Whenever this user is in a server, the server console starts printing this a couple of times per minute for the entire session, and it stops the moment they leave:

Error fetching MarketplaceService receipts: HTTP 504
Error fetching MarketplaceService receipts: HTTP 504 (Gateway Time-out)

As far as we can tell this is the engine’s own receipts poll failing before our code is ever involved. There’s no Luau error attached, and there’s nothing on our side to pcall or retry here, the engine is already retrying on its own (that’s the spam) and it fails every single time for this one user.

What we’ve checked so far:

  • As a sanity check, “m0viix” bought the exact same developer product (3600807455) in the same server while the errors were spamming. It delivered instantly. Only this one user is affected.
  • It follows him across servers and across weeks, so it’s not one bad server instance or a specific version of our place.
  • His dev product purchases in other experiences deliver fine, so it doesn’t look account-wide either. Whatever is stuck seems tied to this user plus our universe specifically.
  • We only assign ProcessReceipt once and it works for every other player. Since the callback never even runs for him, we don’t see how our implementation could cause this, but if we’re missing something on our side we’re happy to be told.

Our best guess is that his pending receipt queue for our universe is either large enough or has something malformed in it that makes the fetch time out. He’s one of our highest volume purchasers, and our experience was also affected by the PromptRobuxTransferAsync receipt bug that got fixed June 3 (Receipt handling error for the new API MarketplaceService:PromptRobuxTransferAsync) in case those are connected. But we can’t see his queue from our side, so that part is just guessing.

Could someone take a look at the pending receipt state for this user in our universe? We’ll honor every stuck purchase in-game once they’re able to deliver.

Info:

  • Universe ID: 5633615594
  • Place ID: 16331682055
  • Affected user: simf (1974853)
  • Working control purchase: m0viix (7727818832), same server, same product, while the errors were live
2 Likes

Thank you for the report. We have assigned this to our team for further review.

2 Likes

Just shooting back for any updates on the subject matter!

Hi @poke_haven, still looking into this. I’m actively investigating, but could you coordinate with the user to check if it’s still happening? That will help ensure we’re looking in the right area.

1 Like

Hi again @poke_haven - I’ve confirmed that your suspicion is correct, the user has more receipts than our servers can process in one go. We’re working on a fix

1 Like

I can confirm as of yesterday it was still occurring.

Hey! Sorry to rush, but is there a possible ETA for when this would be resolved?

Hi again @poke_haven, I was just about to update you. Last night our team deployed a fix that may help resolve this. The affected user can rejoin the game and should get a subset of their receipts. They may have to rejoin multiple times to process all of the receipts. If you can communicate this to the affected user, please do. Let us know if you find out if it resolves the problem or not. Let me know if you have any questions

1 Like

When the affected user first joined, one of his receipts went through, after that nothing. New purchases don’t work, he also rejoined multiple times.