Iâd also like to implement a loading spinner while Algoliaâs grabbing new values (as the user clicks around a taxonomy of templates into various categories, topics, and sub-topics it can take a second or two to retrieve a new list of template values). How can I achieve this? Itâs not clear to me what the âIs Loading?â workflow action actually does or how it behaves and I donât see an attribute that indicates loading.
Please note that we provide general support for our plugins and do not offer consultancy or customization services.
We recommend reviewing the demo page for workflow examples and carefully reading the supporting documentation for successful plugin integration.
If youâre looking for a team to assist with customization , you can consider hiring Zeroqode. By sharing your project details and budget, one of our project managers will get back to you with an estimate.
You canât explain how your plugin works? The documentation for this is pretty unclear re: how âIs Loading?â actually worksâŚdoes it trigger when it starts loading? When itâs done loading? If itâs one or the other, is there a way to determine the opposite (i.e. - if it triggers when it starts loading, how do I know when itâs done)?
Whatâs up with the errors shown? Thatâs a plugin issueâŚ
We donât help with plugin customisation if everything works as it should on our demo page.
Let us try to help you with the errors you encountered above, namely the 2 screenshots you attached.
Please provide us with this information so that we can help you better:
Can you check if the plugin returns at least some data, to make sure the settings are correct? Also, can you confirm if the latest version of the plugin is installed?
It seems that the error youâre encountering may be related to the way the plugin is interacting with conditionals in your app. Even though youâre not directly using the âAlgolia Refresh a Algolia Simple Searchâ action in your workflows, the plugin may still be triggered as part of a background operation when the filters change. This can sometimes cause unexpected behavior, especially if the action is referencing an undefined value or trying to clear a cache that isnât set.
Here are a few general steps to troubleshoot the issue:
Check your conditionals: Make sure that the conditions triggering the filters are properly set. If any condition refers to an undefined or empty value, it could result in the error youâre seeing. Double-check the data source and ensure the conditionals are targeting the correct values.
Review plugin settings: Ensure that all necessary fields and settings in the Algolia Search plugin are properly configured. This includes ensuring that the indices and API keys are set up correctly in the plugin settings.
Use a fallback for undefined values: In cases where a field might be undefined (like a null or empty value), you can add a fallback or default value in your conditionals to prevent the error.
Test in isolation: If possible, try simplifying the workflow or isolating the plugin action to see if the error still occurs. This can help pinpoint the exact cause.
Iâm calling the action in a backend (API) workflow passing the index name âfeatured_product_imageâ and the object ID in in the in âobjectsâ field. It seems to run without error in the logs but eh object still exists in Algolia. Can you advise?
Based on the pluginâs behavior, the âDelete Objectsâ action in the backend workflow will return the ID of the object that was deleted if the action is successful. Could you please check if the action returns the object ID in your logs? This will help you confirm if the object was indeed deleted successfully.
If you still see the object in Algolia, itâs worth verifying that the correct object ID is being passed and that no errors are occurring during the process.
Feel free to share any further details if youâre still facing issues, and we can assist you further!
I just tested again and can see no successful return notifying me it was deleted. I see it calling the Action with the correct ID (which I confirmed exists in Algolia).
Weâre sorry, but it seems there has been a misunderstanding.
The delete function returns a list ofobjectIDs from Algolia that have been successfully deleted by Algolia .
Please take a look at the screenshot below for clarification.
To exclude the current user from the Algolia search results in your Repeating Group, applying a :filtered constraint directly on AlgoliaSimpleSearch A's Result wonât work reliably because Algolia returns plain text results, not Bubble user objects.
Hereâs a more effective workaround:
Option 1 â Filter by ID manually:
If your Algolia record includes the userâs unique ID as a field (e.g., userID), you can filter the results like this:
AlgoliaSimpleSearch A's Result:filtered
with constraint:
This text is not Current User's unique ID
Make sure the field in Algolia exactly stores the unique ID of the Bubble user (not the email or name).
Option 2 â Use Backend Filtering
If filtering on the frontend is too limited, consider using Algoliaâs filters parameter directly in the pluginâs search call, e.g.:
filters: NOT userID:"[Current User's unique ID]"
This gives more precise control and improves performance.
Let me know which method youâre using or share how your data is structured if youâd like help setting it up!
Based on the provided information, the issue with Option 1 not working as expected may stem from a mismatch between the Algolia field (objectID) and the Current Userâs unique ID.
Since your Algolia index (freelancer_profiles) uses objectID as the unique identifier, ensure the constraint is applied correctly:
In the Repeating Groupâs data source, set AlgoliaSimpleSearch Aâs Result::filtered with the constraint objectID != Current Userâs unique ID.
Confirm that the objectID in Algolia matches the Bubble Userâs unique ID exactly (not email or nickname).
Regarding your workflow (âadd objectâ and Algolia settings), the current setup seems to update the objectID and other fields (e.g., displayedRank, nickname) correctly.
However, if the filter still fails, consider Option 2 (Backend Filtering) by adding filters: NOT userID:â[Current Userâs unique ID]â in the pluginâs search call settings.
If the issue persists, please share the exact data structure of your Algolia index or any error logs for further assistance.
Weâre happy to announce a major update for the Algolia Search V2.0 plugin, now with Paginate All Pages functionality!
This update allows you to effortlessly retrieve thousands of records at once, eliminating the need for manual pagination. This enhancement is perfect for users who need efficient data processing, reporting, integrations, or bulk edits.
Still getting the first error every time I search for something. It returns results just fine, but throws this error multiple times in succession every time: