Hey, everyone! We are facing a weird issue related to the "succeed" toast when running an avo action. The problem is that some browsers run perfectly, and in others don't. We recorded some loom videos to help to understand. Error (nothing happens): https://www.loom.com/share/26bd724da03e4b52aab48faaadcfff63 Run perfectly: https://www.loom.com/share/d13c37c81bce4792b89b520aa9ff5d07?sid=3a7d5673-ef16-4ef8-b9c7-d72ab7500f1e Can someone help me with this issue?

Hi @stale-sugar-44403 ! That's weird, I'll check it out tomorrow. So, the same action, same output, but the alert only shows up in some browsers, right? Which browsers work, which don't, and what Avo version are you using?

Exactly. We are using... - gem "avo", "3.19.2" - gem "avo-advanced", "3.19.2", source: "https://packager.dev/avo-hq" And we tested in... - Arc 1.9.4 (worked) - Chrome 136.0.7103.114 -- last version (not worked) - Firefox 138.0.3 (worked) In other words, the problem seems to be with the Chrome.

Got it. I've been trying to reproduce the issue, but I haven't had any luck so far. I did notice that you wrapped the

has_many

association field in a panel. That's actually redundant, since association fields already come with their own built-in panels. It also looks a bit odd visually. Wrapping it in a panel adds an extra white background that creates unnecessary visual noise. I'm guessing your code looks something like this:

ruby
tabs title: "Title", description: "Description", id: :second_tabs_group do
  # ...
  tab "Api tokens" do
    panel do
      field :api_tokens, as: :has_many
    end
  end
  # ...
end

You can simplify it to this:

ruby
tabs title: "Title", description: "Description", id: :second_tabs_group do
  # ...
  field :api_tokens, as: :has_many
  # ...
end

Try this approach with the latest version of Avo. If the error persists, please double-check whether it's happening exclusively on your machine. Let's stay in touch and get to the bottom of it.

Hey, @loud-jewelry-99127 ! I applied the changes you recommended, but the issue persists. 😦

Could you please confirm whether this issue is limited to your local environment, or if other developers on the project have also experienced it?

My IT team is running some tests, but the errors are only occurring on the computers of certain users in the company. I recorded a video instructing some users to clear their cache and session to help determine if that might be causing the issue. As soon as I have all the results, I’ll get back to you.

Thanks Jackson, that will be helpful

Hi @loud-jewelry-99127 ! I’m happy to share some good news... the issue has been resolved! After investigating, we found that the problem was related to the browser cache. Once the cache was cleared, everything started working as expected again. Thank you very much for trying to help. Best regards!

Great news @stale-sugar-44403! Cache-related bugs can be tricky to identify, glad you guys figured it out!