AndreaHenderson Domo Product Manager

It looks like there was an underlying database version upgrade that caused this issue. The team is working to roll back that update, which should be completed by EOD.

Hi all - I've brought this to the engineering squad and we're reviewing whether any changes were made that could have resulted in this. I'll update you when I learn more. Thanks for surfacing this!

@Aaron_Trent @bdv @Michael_Lehlbach1 - we've rolled the code back to revert the issue, you should see it fixed now.

Okay, thanks for that info. I have someone looking at it now.

Thanks for surfacing this. Are you all using window functions in your SQL tiles where you are seeing this issue? Also, can you message me the ticket numbers you filed? I'll ping my engineering squad on this.

@RobbieJannoh Sorry to hear that you're having this issue! How frustrating. The AI Text Generation tile takes advantage of Anthropic's batching services, which offers a significant discount on input/output tokens, however it comes along with varied run times as it runs on idle compute. We understand that these varied runs…

@collinT Wanted to close the loop here, if you haven't already received the communication from your CSM or the resolution to your ticket: In May 2024, we introduced a feature allowing users to specify relationship constraints on join conditions (called "Relationship Type"), including Many to Many, One to One, One to Many,…

Thanks for surfacing this. We're working on figuring out the issue and are hoping to have a resolution soon.

@TejalGovila they should be fully supported in the SQL tile and are in GA so you should be able to use them. What issues are you running into when attempting to use them?

Thanks for sending that over, I'll reopen the ticket and have somebody take a look.

My understanding is that we had released a fix for this bug on August 15th last year. I hadn't seen any reports of it since and presumed it was resolved. Sounds like it still exists for you? I'd be curious to know if anyone else is experiencing it (community, please reply if you are). Is it the EXACT same issue as last…

Good news! This functionality is now in beta, and should be going GA with the January customer release. Feel free to opt into the beta if you'd like to play with it early.

Good news! This functionality is now in beta, and should be going GA with the January customer release. Feel free to opt into the beta if you'd like to play with it early.

Good news! We recently implemented "Run to Here" in Magic. It's currently in beta, and should be out in GA early next year. Feel free to opt into the beta if you'd like it early. :)

This should be resolved now. Please let me know if you are still experiencing issues.

Sorry about that. We are aware of the issue and are working on resolving it.

@paddylillard Hooray! So glad that you're enjoying it and that it's saving you time. We love to hear that.

Fair point! That is super valid use case. (However, I DO see sooooo many people writing CASE statements that should really be lookups, heh.) Unfortunately I'm not going to be at Dallas this year. 😥 I'll be at Minneapolis, Toronto, SLC, and Atlanta.

@PeterFry A fix for this has been deployed. You should see the behavior restored over the next several days (as soon as today). 😁

This is fair feedback. The pop-up was created in response to feedback from multiple other users, asking for an easier way to apply this to their existing DataFlows. If you send me your instance ID, I can force it to on for everything and you'll never see the pop-up again. :)

We have conceived of this as a user-level setting, as each user may have different preferences. In the future, once you set that setting for yourself, it will appear as on for you on every existing and new DataFlow.

@PeterFry This seems like a bug or regression to me. I've filed a ticket for one of the engineers to look at it. Thanks for surfacing this to my attention!

The behavior is for it to go away permanently if you click "Ignore", and that's what I've experienced in my own DataFlows. However, if you click the X (instead of Ignore), that is a temporary dismissal and the pop-up will show up again the next time. It shouldn't show for any brand new DataFlows, only ones created before…

The AI part is going into beta soon and was erroneously turned on for all instances. It has now been turned off. The feedback about being able to collapse parts of the window is great, though, and I have a UX designer and engineer looking into this now.

If you're filtering on that number of values, it might be easiest to create a DataSet containing those values and use it as an input to the Magic ETL DataFlow, at which point you could use a join to filter on those values (inner join to filter to the list of values, or outer join and then subsequent filter to filter to the…

Sorry for the delay, the Knowledge Base article is in progress and should be out soon.

@ArborRose I don't think that pop-up is functioning properly, if you're seeing it on every DataFlow. Thanks for the heads up. I'm going to dive into it with my team. As for the desire to have the mini map closed by default, that's good signal. I will make a note of that as we've started conversations about what things in…

Thanks for reporting this. One of the engineers on my team is working on it now.

@nwcarlson Oooh I like that, thanks for surfacing it.

Thanks for posting this idea! This has been added to consideration in our backlog and will be reviewed by the team.