My trigger in QuickSight Flows was working fine previously, but it has suddenly started failing with the following error:
‘User ARN does not contain AWS account ID’
Nothing has changed on my end. Our admin also confirmed that my permissions at the author level are unchanged. I’ve tried restarting and refreshing multiple times, but the issue persists.
Is there a new AWS update/policy causing this issue?
Hi @datateam and welcome to the community!
Thanks for including so much detail and confirming with your admin that nothing has changed on your side. As to my knowledge there hasn’t been any updates or policy changes that would have caused this. A couple of things worth trying, first, fully sign out of Quick and sign back in to force a fresh identity token. Second, ask a teammate to run their own trigger to see whether they hit the same error, as that tells us whether it’s isolated to your account or something broader. And lastly, you could try duplicating the flow (or recreate the trigger on it) and see if the copy runs cleanly.
If it persists after re-authenticating, this would need someone on the backend to trace why the ARN is coming through incomplete, so I would recommend opening up a support ticket (Case management - AWS Support).
Hope this helps and feel free to update us on any new developments!
