Workflow failing with "admin access required"

Self Hosted Retool
,
1

Hello! We have been having trouble with a workflow. The error message strikes us as weird, and I can not seem to find any information anywhere.

The workflow is tied to the "user created" trigger and it simply creates a new folder for each new user through the Retool API.

I said it is weird because it works flawlessly for up to 3 days, and then it stops working all of sudden. The log states that "Admin access is required" but it is unclear to us what this really means.

workflowFail
workflowFail1337×712 99 KB

As you can see in the image, it fails when trying to invoke the get /folders api call, however if we remove that step, it fails in the next. We manually recreate our token for the api and then it works again for a few days, but is this normal?

Here is our resource config that as you can see, is also very simple, and the "test connection" buttons does return OK. Are we missing something regarding the Retool API tokens?

workflowFail2
workflowFail2920×701 38.2 KB

Thanks in advance! :slight_smile:

2

Hello again, we have been able to understand the issue.

The api token seems to be valid as long as the user who created it holds the admin privileges. In mi case, those permissions were temporary, so the workflow stoped working as soon as they were removed by our back service.

We have created the token using a stable admin, so hopefully we will not see this error anymore.

Just leaving this here in case it might help someone :slight_smile:

3

Glad to hear it, @AlejandroBF! Thanks for sharing this update. :+1: