Workflow functions (that are api calls) are sharing header params

I’m a faily new user however I know my way around a bunch of these no code solutions. Love retool so far, however this one issue I’m having has me super frustrated and confused and I’m 99.999 percent sure it is a bug.

The jist of the issue is that I have a workflow called: Tinkuy: Sync Participants to CRM (Scheduled)

In this workflow I have several functions on the left hand panel for functions. A handful of those functions are api calls. When I change any header params in those api call functions…the header params change in every single function that is an api call. No other parameters in the api call functions are behaving this same way…just header parameters.

I made a vimeo video of it so that it would be easier to see what it is that is happening (FYI the api keys visible in the video are not active):

Help!

1 Like

Definitely a bug. Were these functions created independently or were they duplicated from other functions?

I have had a similar issue with items in JS Code (specifically variable names) being renamed when updating setups in functions.

@Darren @Paulo could this be related to the linked issue?

ETA: Welcome to Retool!

That's the first thing I thought of as well, @pyrrho. I will get in a bug report as soon as possible, as this seems not so good. :sweat_smile:

Welcome to the community, @Marcelo_Fernando_Vigo! Thanks for flagging this.

Some of thre functions in question were duplicated......and I actually thought that might be the issue, however I then created a completely new function api call and the issue was the same. It's definitely affecting ALL api call functions.

Thanks Darren. I'm definitely glad it is only affecting the headers and not the other gui fields.

1 Like

Fair enough, but even that seems pretty troublesome! I appreciate the thorough documentation of this issue, @Marcelo_Fernando_Vigo. It's on the roadmap for our engineering team and I'll continue to provide updates here until the fix is live. :+1:

In the meantime, you should be able to get around this issue by pre-defining all your REST API queries as separate resources. Thanks again!

Ok. I await the update. The api calls in that workflow need to be dynamic because the api-keys and particulars about the api calls are based on an organization table.

1 Like

I think it should still work! When defining queries in the Query Library, you have the option to specify which parts of the query are variable and can pass in the necessary parameters when triggering the query:


I worry that you might run into a similar issue if you use multiple "copies" of the same query, though. :sweat_smile: