I am using the Orchestra plugin inside a repeating group.
Say I have 10 standard shopping items. This week, I decide I only need eight items from the list.
I remove the two items from the repeating group. When I click the action to trigger the musicians, the ten items still get pushed through.
If you inspect the elements, you can see the removed line items are still there but invisible.
I tried resetting the repeating group, resetting inputs, and reinitializing musicians, but to no avail. The only way to clear it is to refresh the page.
Any ideas? @ZeroqodeSupport
1 Like
Hey Jeff 
Have you tried adding a condition to the musicians workflow so it only runs if “this musician is visible”?
I’m also curious how you’re updating the RG data source when you remove the items and what kind of resetting you’re doing every time you click the action to trigger. It’s possible you may have conflicts from previous runs before you removed items?
3 Likes
You got it. I missed that one.
I added the “this musician is visible”? condition and it worked.
Thanks Gaby…
I am pulling the RG data from a State. When I remove the data, it updates the state.
2 Likes
Just came across this and will be trying the same - thanks for the suggestion.
I actually submitted this a possible bug to Zeroqode last night but have yet to hear back.
I am using the Orchestra plugin to do this in a Table element and it does not appear that the indexes refresh when the data source changes.
For instance, I have a table of items with a data source that includes a search constraint equal to a user dropdown. If I change the dropdown to a new user, the table updates, but when I trigger the musicians, it is running and calculating off the old position of data/rows. This is especially problematic if the table contains more or less rows between the two users.
I have tried everything to get the data to refresh including using states to hide/unhide the musicians, the tables themselves, and so on, but was not successful. My next step is to try to fork the plugin code and write a refresh piece if needed.
It does appear this is working for me as well in brief testing. I had tried to attach this to the step inside the workflow (which is not an option) vs. the workflow itself. I’m guessing there’s some caching going on here as stated by the OP where it’s hidden vs. actually gone/refreshed.
1 Like
I did hear back from Zeroqode support that this issue could be due to them not fully certifying the plugin for use with table elements. I informed them of this thread and how this was definitely an RG problem as well.
They suggested another likely workaround of clearing the data source and then adding it back after a brief delay as a way to reinitialize all musicians.
Update 2/25/25
Closing the loop - clearing the data source does not reinitialize the musicians and Zeroqode may look to fix this in a future update.
Hello Everyone - I spent hours working on this issue, I managed to resolve it; Even tried dynamically generating the musician name and moved the element into reusable element - Same issue with triggering musician’s that I no longer needed; which is painful if you’re iterating on a list within a list; even tried forking and fixing the issue myself!
To fix it, I added a condition to check if “this musicians Index > Repeating Group List Count” it would terminate and that appears to have solved the issue.
Hope this helps someone.
Spent 3 hours this morning coming to this conclusion. It seems Musicians gets stuck/locked in on an arbitrary number of items, and no amount of “clear list” or “Display list” will resolve it. So if the source data changes in any way, it will cause issues. Adding the “only when this musicians is visible” condition solved the problem, but feels like a very hacky way of solving it - will feedback to Zerocode on their forum as well but has cost me a morning and throwing in god knows what silly conditions and timings elsewhere in the app trying to get to the bottom of it.
With that said, its an absolutely amazing plugin without which a lot of functionality would just be unfeasible.
1 Like
To add - what’s equally strange is that initially I was using ListShifter but was experiencing problems with it not firing properly which I couldn’t get to the bottom of, hence I shifted over to Orchestra for an alternative approach. But now this has me thinking that its unlikely they are both bugging out at the same time so wondering if something under the hood is amiss with Bubble itself here…
