I am using a standalone Amazon Quick account created through quick.aws.com (Plus trial).
I configured a Gmail action connector with Managed OAuth and linked it to a custom chat agent. The connector shows Signed in and Ready, and CreateDraft appears under Enabled tools.
Expected behavior
After the user confirms, the custom chat agent should invoke CreateDraft and create a Gmail draft without sending it.
Actual behavior
The agent reports that Gmail is unavailable or that it cannot access the Gmail account. No action reaches the connector, and the connector’s Usage tab remains empty.
Troubleshooting already completed
Reproduced in both Comet and Google Chrome
Allowed pop-ups and third-party authentication
Verified that the Gmail mailbox is active
Signed out and reauthenticated the connector
Removed the original connector
Created a new Gmail Managed OAuth connector
Linked only the new connector to the custom chat agent
Selected Update preview and launched the latest agent version
Tested both Preview and a new conversation with the launched agent
Confirmed that CreateDraft is enabled
The issue is reproducible in both Preview and the launched agent. The connector is Signed in and Ready, but Usage remains empty after every failed attempt.
Could AWS please check whether the user-auth token association or action connector registration is missing or stale? This appears similar to an AccessTokenNotFoundException, although no technical error code is displayed in the chat UI.
I can provide account-specific identifiers privately if needed.
Thank you for providing so much detail about this issue and the trouble shooting steps you’ve already taken. Since this is a public facing form, we do not have access to individuals account and since you’ve already done what we would have recommended and there doesn’t seem to be much change, I would highly recommend creating a support ticket (Case management - AWS Support) to get further assistance.
Hope this gets resolved and feel free to keep us updated!
Thank you very much, Cesar, for taking the time to review the issue and for pointing me toward AWS Support. I really appreciate your help.
I tried to open AWS Support Case Management, but the sign-in page requires credentials for a standard AWS account.
This Quick environment was created as a standalone Amazon Quick Free/Plus account through quick.aws.com using Google sign-in. The signup confirmation identifies it as an ACCOUNT_MANAGEMENT_LITE_SIGNUP_CONFIRMATION. I do not have a root user, IAM user, AWS Console credentials, or access to AWS Support Case Management. In Quick, the Support option routes me back to this public community.
Could you please advise how a standalone Amazon Quick customer can open a private account-level support case? If there is a Quick-specific support channel or another escalation path, any guidance or introduction you can provide would be greatly appreciated.
I can provide the Quick account identifier privately if an authorized support representative contacts me.
Thank you again for your assistance and for supporting the community.
Thanks for the follow-up, and good catch. You’re right that the standard AWS Support Console requires AWS account credentials that a standalone Free/Plus account created through quick.aws.com won’t have. Standalone accounts have a separate support path that lives inside the Quick web app itself rather than the AWS Console. If you open the account management area from your profile in Quick, there’s a Support section there for submitting a request, and it doesn’t require a root user, IAM user, or Console credentials. It’s also worth having your Account ID on hand from your account settings, since that’s useful when you open the case.
