REST API resource unauthorized when in workflow run

Queries and Resources
1

  • Goal: I have a REST API resource that works when I run the component separately but does not work when the workflow runs as a whole.

  • Steps: I have removed the resource and created it again, and also used the token that it generates in a manual API request from another application and it seems to work. I think the issue is with the defined variables

  • Details:

  • Screenshots:

    image
    image1671×910 137 KB

  • App json export:

3

any update on this bug? this setup was working perfectly before and without any changes the workflow started to fail. it makes no sense, if I use the token created by the resource hard coded in the workflow component it works, or if I run the component manually with the defined variable from the resource it also works...but when the workflow runs normally it fails. this is really affecting the usage of one of our main resources/workflows

4

sorry, I just tested and this is working perfectly again (yay!)
I guess it would just be good to understand what happened so that it doesn´t happen again.
In cause there was any intervention here, thanks for the quick resolutions guys.

5

Hey @ricardoguerreiro! Thanks for reaching out.

I'm not positive, but it sounds like the workflow is using an expired auth token. In case it does break in the future, can you share more information about how this resource is authenticated?

6

hey @Darren its happening again. the token is authenticated in the resource, and the component runs the request by its self successfully, but then the workflow fails. can we maybe connect to show you this? has to be a bug somewhere

7

It certainly sounds like a possible bug. We host office hours every Tuesday and Thursday from 11am - 12pm PST! Drop by and we'd be happy to help you out there. If that doesn't work for whatever reason, you can try sending me a screen recording via DM. :+1:

1 Like
8

i was declaring "access.token" twice in the resource. even though with different variables names they were coming from the auth flow and the refresh flow. since I didn´t need the auth one cause I use the refresh, I removed the extra variable and it seems to work fine now. thanks for the help @Darren