Hi, guys. We noticed an issue today when creating ...
# gooddata-cloud
t
Hi, guys. We noticed an issue today when creating [tokens via API](gooddata.ai/docs/cloud/manage-organization/user-token). If you create a token and then use it immediately after, it sometimes may return 403 Unauthorized. I guess there might be some problems with replication / eventual consistency there, because when we added sleep after token creation everything started to work correctly again 🙂 It might be worth looking into it / mentioning this in the docs, if that behaviour is expected. (noticed on cogvio.cloud.gooddata.com)
k
Thinking completed Great observation, and your diagnosis is correct. This is consistent with GoodData's eventual consistency behavior on write operations via the API. As noted in a related support thread, GoodData's declarative/entity APIs are eventually consistent — a
201 Created
response confirms the write was accepted, but full propagation across nodes takes additional time. The same pattern applies to API token creation: the token exists in the system after the
POST
, but it may not yet be recognized by all nodes when an immediate request is made with it, resulting in a transient
403
. Your workaround (adding a short sleep after token creation) is the right approach for now. The recommended general pattern for this type of workflow is to poll with a GET until the entity returns
200
before using it downstream — a 1–2 second retry interval with a ~30 second timeout is typically more than sufficient. [User Tokens] Regarding the docs — that's a fair point. The eventual consistency caveat for token creation isn't currently called out explicitly in the API token documentation. [User Tokens] To help the Support team investigate and consider a docs update, please add the following details to this thread: • The approximate time(s) the
403
was observed • The delay (sleep duration) that resolved the issue for you • Whether this happens consistently on first use of a new token, or intermittently on existing tokens as well • Any trace or request IDs from the failed
403
responses The Support team monitors this thread and will pick it up from here. Community support (Startup & Professional): You're already in the right place — the GoodData Support team monitors this Slack and a team member will join the conversation when human review is needed. You can also visit the Community Forums for additional discussion. 24/7 Support (Enterprise plans): If your account includes 24/7 Support or this is a Severity 1 (L1) critical issue, you can also submit a ticket, email support@gooddata.com, or call +1 (415) 200-0194. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.
t
• Observed from Monday 2026-11-02 08:00 UTC • 1 s was enough to fix the issue • only when creating a new token, token works fine afterwards (but since it crashed our transaction, we rollbacked and in next request we tried to request a new token...) • I am not sure I have one, but check Cogvio requests
s
Hi Tom, Thanks for flagging this. Confirming this is expected behavior. A brand-new token can take a brief moment to propagate, so using it immediately can occasionally fail. Your delay workaround is the right fix.
👍 1