First time reporting a bug? Refer to our Start Here post.
Team ID:
yM8sW3aEYFsFbzPsDOik
App ID:
ZZ6GVz0BxFIsC9blPnyJ
Description
I have some scenarios on make involving glide modules. => get rows / edit row / create row
Any Glide module is fialing with a runtime error (that occures imediatly)
How to replicate
here is a loom :
The error suggests that it isn’t finding the Glide Table.
Is the integration still enabled on the Glide side?
Was it ever working?
What happens if you create a completely new scenario and add a similar module?
I would suggest to verify your connection to Glide in Make.
You find it under connections in Make.
Click verify and see that everything is OK.
I have the same problem. The error occurs sporadically without anything being different in the workflow or in Glide.
Even “Sleep” modules don’t help. It’s as if the row is missing.
For me, the error occurs after submitting a form. When the form is submitted, a webhook is triggered after 5 seconds, which then calls the “get row” module after another 2 seconds of “sleep”.
Despite the many pauses, this runtime error occurs.
Does anyone have any advice?
Thank you very much!
Best regards
Bernd
If you try to get a row that was added a while ago, does it work? You can try to run just that Glide module to check.
Yes - I had already tried that.
You can’t say for sure, but data records that are “older” don’t seem to cause the problem.
Let’s circle back a bit. Can you tell me why you need to get that row from Glide, right after it was submitted? What piece of info do you need from that row?
sure - there are 2 reasons why you need to do this.
of course, in case 1 you could pass the keyword directly to the webhook.
In case 2, I still need the availability of the row relatively quickly.
Is there a time during which the row is available in any case?
If I knew that, I could set the sleep modules directly to it.
Or do you have another idea for this?
Thank you in any case!
Yeah, I was thinking this when I asked you the question, so you know what’s up.
So something like a status of it’s being run at the moment, please wait, inside the app? I guess you can set some value in Glide to display that message, then clear that using Make when the scenario has finished running? Or a visibility condition based on a field that is sure to not be empty when the scenario has finished running.
that’s great and absolutely necessary. when will it be released?
Yes, that is certainly possible.
However, if the workflow takes 30 seconds, you may want to give the user some feedback in between and then you have to call up the row.
ok, but then you only call up the row after 10-15 seconds and not after 2 or 3 seconds.
Not sure what you mean by release, sorry if I’m misleading you, but it’s not related to any immediate release.
Yeah, this UX makes sense to me. What’s the average time that your workflow runs?
ok…
as mentioned, the workflow runs about 30-45 seconds.
