Array remove function adds second set instead of removing item

Hello,

I feel I dont understand the logic behind the remove function:

I am updating tags array (in livespace module) with a formula:
{{remove(4.tags; “testowy”)}}

I am updating the same array.

Effect is: it adds a new set of items to old array, and this new set of items have indeed this specific tag removed.

What Im doing wrong here?
P.

Welcome to the Make community!

What is the output of module [4]?

To allow others to assist you with your scenario, please provide the following:

1. Relevant Screenshots

Could you please share screenshots of your full scenario? Also include screenshots of any error messages, module configuration fields, and any filter settings. We need to see what you’re working with to give you the best advice.

You can upload images here using the Upload icon in the text editor:

2. Scenario Blueprint

Please export the scenario blueprint. Providing your scenario blueprint file will allow others to quickly recreate and see how you have set up the mappings in each module, and also allows us take screenshots or provide module exports of any solutions we have for you in return - this would greatly benefit you in implementing our suggestions as you can simply paste module exports back into your scenario editor!

To export your scenario blueprint, click the three dots at the bottom of the editor then choose ‘Export Blueprint’.

You can upload the file here by clicking on this button:

3. Output Bundles of Modules

Please provide the output bundles of each of the relevant modules by running the scenario (you can also get this without re-running your scenario from the History tab).

Click on the white speech bubbles on the top-right of each module and select “Download input/output bundles”.

A. Upload as a Text File

Save each bundle contents in a plain text editor (without formatting) as a bundle.txt file.

You can upload the file here by clicking on this button:

B. Insert as Formatted Code Block

If you are unable to upload files on this forum, alternatively you can paste the formatted bundles.
These are the two ways to format text so that it won’t be modified by the forum:

  • Method 1: Type code block manually

    Add three backticks ``` before and after the content/bundle, like this:

    ```
    content goes here
    ```

  • Method 2. Highlight and click the format button in the editor

Providing the input/output bundles will allow others to replicate what is going on in the scenario, especially if there are complex data structures (nested arrays and collections) or if external services are involved.

Sharing these details will make it easier for others to assist you.

Update: I noticed that this module behaves like that in consistant way. If I modify field tags with anything (like “another tag”) Im going to get the previous tags array with “another tag” added. So it is like built in push function. So question is how to work around that?

Thanks for your reply. I made a minimal working scenario to reproduce this issue.

So, when a record is modified, and includes specific tag:

I want to remove that tag.

Incoming data is:
image

It passes correctly through the filter,
then in module 8:

but the effect is:

image

Blueprint:
blueprint (1).json (19.0 KB)

Try using the built-in function join

e.g.:

{{ join(remove(1.array; "testowy"); ",") }}

Screenshot_2025-02-27_160253

For more information, see the join function documentation in the Help Center and do the tutorials in the Make Academy.

If this doesn’t work, then it’s a bug.

Hope this helps! Let me know if there are any further questions or issues.

@samliew

P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.

Thanks!

Your formula doesnt add new things to array, but also does not remove desired element.

Probably the solution lies in the thing I noticed in my update:

Update: I noticed that this module behaves like that in consistant way. If I modify field tags with anything (like “another tag”) Im going to get the previous tags array with “another tag” added. So it is like built in push function. So question is how to work around that?

Does it help or you still believe it is a bug?

P.

Aha, it really does appear to be a bug then!

According to the Official Livespace API documentation, there should be two separate fields:

  • tag_add — tags to add

  • tag_remove — tags to remove

Looks like Make needs to also add a field so you can specify tags to remove.

For technical issues or bugs like this, directly contacting support can often lead to a faster resolution. They have access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to.

You can open a new ticket here, or if you are unable to login for some reason, you can create another new free account to access the ticketing system (which is only available to logged-in users). After submitting a new ticket, you will receive an automatic confirmation email with the subject “Ticket Created” in the subject. If you do not receive this, try sending the ticket again.

If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.

In the meantime, you can use the Universal module with the correct fields.

If you need assistance in setting up the app’s universal module, or the generic HTTP module, please provide additional information about what you have tried with regards to the external service’s Developer API Reference – how you are setting the connection up, a link to the endpoint are you trying to connect to, and what errors you are encountering.

You can also complete this brand new course/tutorial in the Make Academy on how to use external APIs — API calls with HTTP modules

  • API and Endpoints
  • Header and body
  • Multipart/form-data
  • OAuth 2.0

Hope this helps! Let me know if there are any further questions or issues.

@samliew

P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.

Thanks for that! I already submited a ticket, meanwhile I will use a generic api request module, thanks!