If your workflow actions donât depend from each other, then create 4 workflows events for âWhen popup is openedâ instead of only one. It may be that this activates them all at once.
Donât have any other idea
Maybe @Jici could give a try.
Just asking⊠but why you need to wait for your popup to open to load the list in the repeating groups? Canât you load them before? This may speed up the processâŠ
@rpetribu Because the data on the popup is dependent on the RG row the user selects (each row is a business name and each popup is the detailed business profile)
Your list on RG should probably be based on the Parent Popup data. You shouldnât need to use display list in RG because the Data source should be based on the popup data. When this is updated, Bubble will also update the result of the RG. I donât know it will fix the sequentials run, but it may faster the whole process.
@Jici Display lists are necessary for popups that use API data.
This is because bubble only calls APIs on popups just once in total, meaning that if you close the popup of business #1, its data will show for business #2.
@EliteDataEngineer This apply to all API Call (not just in Popup) only if thereâs no modification in your API Call. If you change your popup and the RG call is base on the Current popup data, this mean that the call should be different and Bubble will request it again.
So what do you push to your popup as display data is involved I guess in your API Call and because of that, The RG will update itself from the popup data source update (only if this is used in your API CallâŠ)
Iâve made a test and can confirm that in this case, the RG will load parallel and not sequential. (Made a test where I have a first API Call that is used into 2 different RG group call and theses two load parallel after the first one is done)
@Jici Your suggestion pointed me in the right direction by making me revisit âData Sourceâ as an option instead of âDisplay Listsâ.
My API requires the current datetime as a parameter, which bubble wasnât refreshing on the popups. I therefore ended up setting the datetime as a custom state which allowed me to go back to using data source, which now gets the calls being made in parallels!