Into the workflow, parameters don’t show up.
It’s a bug? Anything to change?
My wild guess is this: You have two queries named buscar_pedido_por_id. One is without any parameters.
nono. It’s happening since today. Previously, it worked fine.
It happen on every others query too .
More details:
It happens when type of parameter is number.
I have the same issue. Now when I click on any query, it won’t bring the popup to specify the parameters for the SQL Database Connector. I opened a bug. Mine just started a couple hours ago.
1 Like
I have the same issue with the SQL Database across all existing in new and existing queries. API calls are ok. I am talking with support and will make them aware of this thread.
1 Like
same issues. it was working fine yesterday, but today the parameter is gone
1 Like
I use MS SQL Server with parameters in the SQL connector and everything is fine in my app. Which SQL version are you using?
where do I check the mysql plugin version?
The Database Type I mean:
But it might be this issue, reported here instead: SQL Database Connector Bug on Number Parameter - #2 by rjroland
I only saw this afterwards. Most of my parameters are text, which could be why I am OK or haven’t noticed an issue.
i am using mysql… and the one that disappeared is a date datatyle 
Looks like anything that isn’t a text parameter is doing it:
All the non Text Parameters are missing!
So not related to Database type. It is a Bubble bug!
Lucky for me my users are having a public holiday today, so I didn’t notice.
1 Like
Update:
It seems the parameters issue is fixed. 
Altough, When I use the queries, give me this error 
Happens on dev and live
No more information
I had published to live, while the issue was present, unbeknownst to me. This morning it was fixed in my test version, but users in my live version continued experiencing difficulties. I republished to live and these issues disappeared. This is the first time I’ve noticed this behaviour. I don’t think your issue is related though.
1 Like
Upload a new version, nothing happens unfortunately.
“When a temporary bug happens” is there. Live and dev
You may want to try re-initializing the query. Very frustrating indeed!