Candy AI Monthly Tokens Missing? Check the Replenishment Date

A missing Candy AI monthly token allocation is a date-and-account question before it is a purchase question. The replenishment help article ties the monthly refresh to the subscription anniversary. It does not say that every account receives tokens on the first day of a calendar month.

This guide helps you organize an expected-credit discrepancy. We did not inspect a paid balance or measure the timing of a live allocation.

There can be two different clocks

The paid-user help page distinguishes monthly token allocations from annual subscription billing. An annual subscriber should therefore avoid using “I was not billed this month” as proof that no monthly allocation is expected.

Consider an illustrative account first subscribed on the twelfth. Its relevant monthly checkpoint is connected to that subscription date, rather than a generic calendar reset. This example is not a promise about the exact hour, time zone or treatment of a short month. Ask support about those edge cases when they affect your account.

Build a small expected-credit timeline

Record the account identifier, plan, original subscription date, expected allocation date and the balance you observed. If available, keep transaction or usage history that can explain changes around the checkpoint.

Separate an allocation from a remaining balance. Seeing fewer tokens than the nominal allocation does not, by itself, establish that the full allocation never arrived; later usage could affect the number. Conversely, having an active subscription does not show that a particular crediting event completed correctly.

Observation	Question to resolve
Annual payment is months away	What monthly allocation date applies to this account?
Balance changed around the expected date	Was this an allocation, usage or another adjustment?
Two devices display different balances	Are both showing the same account and current account state?
Expected date is near a month boundary	Which date and time-zone rule does support apply?

Avoid adding a second problem

Do not buy an additional package just to force the balance to update. A new purchase adds another transaction and makes the original discrepancy harder to isolate. Likewise, do not cancel and resubscribe merely as a refresh test.

Preserve the current records, revisit the intended account screen and note any error. If one device differs from another, compare identities before clearing app data or signing out of a working session.

Send an allocation-specific report

A useful support message identifies the plan, relevant anniversary date, observed balance, observation time and what history is visible. State that you are asking about the included monthly allocation, rather than a separately purchased package.

Use a redacted image only when it helps show the discrepancy. Keep unrelated conversations and payment details out of the report. The practical goal is a confirmed explanation or correction for one account event, not a speculative assertion about every subscriber’s balance.