REST_API not accessible on Retool Production

Subject: Retool Production App Failing to Create JIRA Card (Works in Staging)

Goal: To successfully create a JIRA card from our Retool Production application when a case is assigned.

Problem: The JIRA card creation query fails silently in our Production environment. This exact setup, resource, and query function perfectly in our Staging environment.

Resource Details

  • Resource Type: REST API

  • Authentication: JIRA API Token (stored as 'password' in the Retool resource configuration).

Staging vs. Production Observations

  1. Authentication: After a resource is migrated to Production via Github, does the encrypted API token (password) need to be re-entered manually in the Production resource settings?

  2. Permissions: Does the JIRA_CLOUD resource in Production need to be explicitly mapped or granted permissions to the user groups who are running the "assign case" query?

  3. What other root cause, despite the app code being identical to Staging?

1 Like

Hello @Satyam_Mooloo,

Are you synching the REST API resource across Spaces or across separate Retool instances?

1 Like

Hi Team,
@Jack_T
Yes, the issue is that the resource were not in Sync when i move same from Retool Staging to Retool Prod. But after inserting password for this resource on Prod and save again, it’s finally working now.
I wonder if this was the proper step to do it or was there something I missed.

For instance, when I create resource on staging and put all credentials, it’s working correctly for staging mode.
However, when sending app to Prod and resources, i protect the app/resource, a Pull Request is sent to Github.
After Review and approval (merge and squash), the app and resources are correctly sent to prod.
But the issue is with my resources, since admin prevent me from editing my resources, is there any correct way to store the resources credentials at source so as not to seek admin intervention to put my credentials again.
Please advise.

Regards

Satyam

1 Like

Hi @Satyam_Mooloo!

Great to hear that you were able to get things working by inserting the password for the resource once it was copied over to Prod and then saving the change to lock in the config.

Let me double check with the team on if this is the expected flow and if we have any recommendations for this process.

Let me just clarify your set up, are Staging and Prod two different Retool instances? Or a single instance with the environments set up at the Resource level?