Hi,
I'm just trying to run queries in Workflow editor.
Internal Error running a block: Error: Internal server error
Every database query is failing, regardless of whether it's SQL, GUI, delete, update, upsert.
The workflows themselves are still running, but I cannot run/test any queries from the editor.
I am also getting this on all of my workflows!
On database queries or API requests. All of my blocks fail when trying to run them individually, however if I run the script as a whole, it seems to work just fine
Support,
I noticed around 1230 EST I was no longer being able to rerun components that were running and testing fine just earlier today.
Here is a picture of the error using a simple select statement:
I have checked multiple workflows and both which were working - are both presenting the same error.
Also I verified that the DB connections are working...
Respectfully,
Roberto
Thanks for reporting this too, Roberto!
Another user is having this issue here
The problem has been present for me all day too. Was just about to post again as I imagine it is occurring for more people than it seems!
I'm getting the same thing here, does anyone have an update on this??
Our friend Roberto posted another topic here with the same problem!
Hi Retool community,
I'm encountering an issue with a workflow that had a resource query, retool database, using SQL. Since today, I'm getting the following error:
{"data":null,"metadata":{},"error":"Internal Error running a block: Error: Internal server error"}
Previously to notice this error I did these changes:
I added a new column called segmentation to one of my tables and updated my SQL query to include this column.
What I've tried to fix this:
Interestingly, the same SQL query runs perfectly fine from the query library, so I don't think it's a syntax issue:
It seems like this might be an internal error unrelated to my changes. Could you please help me fix this?
Best regards,
Jude
I appear to be back in business! Workflow components are running again individually!
Would love to hear if the engineers found anything or if it was user error
Hey Judith!
There are a couple of other tickets like this, I have been having the same issue until about 5 minutes ago!
Here is one of the other posts
Mine is back too, thanks for informing!!
Hey all! Thanks for reporting this so quickly. 
We were able to identify an issue with the advance rollout of cloud version 3.89 and have reverted anybody affected back to version 3.87, so this should be resolved!
