Troubleshooting

I cannot sign in after registration

Confirm the email address using the verification message first. Check spam or junk folders and make sure you are signing in with the same address. Password reset and verification links can expire; request a fresh link rather than reusing an old one.

A subscription is missing

Check the active workspace in the app header, then clear list filters and search. New records belong to whichever workspace was active when they were created. Cancelled records may be hidden by the active status filter. Deleted records are excluded from app results.

Dashboard totals look lower or split

RecurLens separates totals by currency and does not convert between them. It also normalizes yearly subscriptions into monthly estimates and monthly subscriptions into annual estimates. Check the original amount, currency, billing cycle, status, and renewal date on the subscription.

A renewal or reminder is not where I expect

Dates are stored as calendar dates and API timestamps are UTC. Confirm the next renewal date, reminder lead time, contract end date, and notice period. Review suggestions are deterministic alerts; they do not modify the record.

An Agent/API request returns 401 or 403

1. Confirm the Authorization header uses Bearer <token>.
2. Check that the token is not expired or revoked.
3. Confirm the URL workspace UUID matches the token's workspace.
4. Confirm the token has the operation's required scope.
5. Create a new token if the secret was not saved when originally shown.

Never paste a real token into a support message. Include the response requestId, HTTP status, operation name, and sanitized request body instead.

A request returns 400

Compare the request against the API reference. Common causes are unsupported fields, malformed UUIDs, dates that are not YYYY-MM-DD, amounts that are not two-decimal strings, and limits outside the documented range.

A governed write did not execute

Proposals expire after 15 minutes and must be reviewed by the same signed-in user to whom the originating token is bound. That user must still have workspace write access. Execution can also stop if membership changed, the token quota was reached, the target record version changed, or the idempotency key conflicts with different input. Prepare a new proposal only after resolving the reported error.

Still stuck?

Export important workspace data before risky changes. When reporting an issue, share the steps, expected result, actual result, browser version, and any requestId—but never credentials, tokens, cookies, or private financial data.