I have a number of backed workflows saving images in the DB. I apply [
imgix to these. The app is throwing errors and these options are no longer available. Has anyone else experienced this? if not i’ll do the bug report thing.
Same, have logged in this morning to well over 300 errors related to the “process with imgix” feature. Backend and frontend are both throwing issues for me. Very Frustrating.
@grace.hong 
Possibly new editor issue
I ended up logging a bug report and it’s been received and escalated so hopefully there’s a fix in place shortly.
"Thank you for reaching out about the issues you are having with the process by Imgix feature. I want to assure you that your report has been received and reviewed by our team.
In order to provide you with the most effective assistance, I’m escalating your report to our Tier 2 support team. They operate Monday to Friday, from 9 AM to 6 PM EST. You can expect a prompt update from us, which may include further questions to ensure a comprehensive resolution.
I truly appreciate your patience in this matter. Considering the specific nature of your concern, our Tier 2 support team is well-equipped to offer you the most thorough solution possible."
I used to save an image to the dB in a backend workflow and apply imigix in the same step. This is no.longer available. Now you can make a change to thing in the next step of the workflow and apply imigix to the image saved in the previous step. In summay this is what I got back from the bug report. Works just dandy although I need to fix the errors
1 Like
Update from Bubble Tier 2 Support
"Our engineers pushed a change recently that exposed some issues that have been present for a while but were not showing up in the issue checker nor preventing deploying apps to live until now.
The engineering team identified an issue where the issue checker wasn’t verifying backend workflows on deploy, and released a change that made sure the issue checker was verifying backend workflows on deploy. However, when it found those issues, the issue checker code would not display the issues in a way that would allow (you / the users) to view the errors and correct them.
It is important to note that the issues found by the issue checker were not ghost issues, but rather real issues that were not being detected until now."
I’m not sure how that is related, unless they are admitting :process with imgix was an invalid operator to chose from in backend workflows…
Exactly my thoughts, I get that the error messages might not have been showing. But I too am reading between the lines here that a change has been made to the “process with imgix” operator.
Have gone back to tier 2 with this query as that’s major change in my mind as I’ve been using that operator in its current format for a long while now.
1 Like
They probably bundled your ticket in with the rest of the people reporting more backend workflow errors now, hopefully its just an issue with their imgix operator choice
Fingers crossed otherwise it’s going to be a long day fixing over 300 instances of this specific error in my backend workflows…
1 Like
Well my concern is there still the imgix option available for you to re-select and fix each one? or is it like not even there anymore:?
Latest update:
“Because the :saved to s3 returns a file and because the :processed with Imgix can only be used on a image, expressions that contained “:saved to S3:processed with imgix” should have been flagged as an issue in the Issue Checker.”
So in the end, it’s a 2 step process as per above. There’s been a bug in the error checker for quite a while that wasn’t correctly identifying this issue at the build/compile stage which while being frustrating, is understandable.
1 Like
This topic was automatically closed after 70 days. New replies are no longer allowed.