18 replies

My workflow stopped working without modifying it

After days of positively testing the performance of my app with the new BuildShip API call, just when I was going to release my new app version to production, the API call has stopped working retrieving the message: Invalid expression: Cannot read properties of undefined (reading 'map')

I debugged it as much as I could, I confirmed the mapped value hasn't changed, I didn't modify the workflow after shipping it, I didn't modify my Firestore database, I confirmed everything that Gemini suggested me to check, and I couldn't find any error.

It's urgent

The support ticket is: #222665

AI Support•5/29/25, 10:13 AM

AI Support Bot Information

@1026190854693605436 you can react on the relevant answer (message) with a

in this thread when you think it has been solved, by the bot or by a human!

Anyone can react on this message with a

if the GPT bot is unhelpful or hallucinating answers.

Please note: Team members will review and answer the questions on best efforts basis.

AI Support•5/29/25, 10:13 AM

AI Response

I wasn't able to find specific information about your issue in the provided files. It seems the details of the situation you described may not be included in the documents I have access to.

For the error message "Invalid expression: Cannot read properties of undefined (reading 'map')", it's typically associated with attempting to call

.map()

.map()

on data that is

undefined

undefined

. You might want to:

- Double-check the workflow execution path leading to the node where this error occurs.
- Ensure the data being passed to the

.map()

.map()

function is defined at runtime.
- Review recent changes or deployments which might have inadvertently affected data structures.

Given your critical situation, I recommend reaching out to in-app support with the ticket number #222665 for more immediate assistance.

BuildShip AI Support

•

5/29/25, 10:13 AM

Gaurav Chadha•5/29/25, 12:42 PM

Hi, I see your workflow was last shipped on May 7th, so no changes in the flow, which indicates no error in the workflow, to verify the correct data is sent from your clientside(frontend) can you please add a log node and log all the inputs you are sending to lastEndedAtThemelastEndedAtTheme node?

Gaurav Chadha•5/29/25, 12:43 PM

@Luis ^^

LuisOP•5/29/25, 12:47 PM

How do I do that?

LuisOP•5/29/25, 12:49 PM

If you check the workflow logs in BuildShip you can see that it stopped working this morning for the production and testing executions. The logs I have come from BuildShip so I guess you have access to them

LuisOP•5/29/25, 12:53 PM

the inputs sent to lastEndedAtTheme come from the previous node, you can check them in the BuildShip workflow logs and in test it with the default value saved for testing

Gaurav Chadha•5/29/25, 12:57 PM

@Luis I've just now sent you an email with a remix of your flow, can you refer to the email and let us know?

LuisOP•5/29/25, 1:06 PM

I don't have access

Captura_de_pantalla_2025-05-29_a_las_15.06.00.png

Gaurav Chadha•5/29/25, 1:16 PM

Okay, we are checking the remix, issue for now. I'll paste the workflow on your workspace to test.

Gaurav Chadha•5/29/25, 1:18 PM

Added the flow as #222665, can you test (ref to email) @Luis

LuisOP•5/29/25, 1:22 PM

ok, let me check it

LuisOP•5/29/25, 1:28 PM

ok, I added my testing data and found the same issue and it doesn't even recognize the uID in the lastEndedAtTheme node.
Also, shouldn't the node idThemes output be set as array?

LuisOP•5/29/25, 1:29 PM

The node uID input should come from the workflow input

LuisOP•5/29/25, 2:22 PM

Any updates?

Gaurav Chadha•5/29/25, 4:43 PM

Updates the flow #222665 the logs indicates that the output returned by idtheme is actually an object instead of an array. You can confirm this by checking the logs during a test run.

To resolve this issue, you will need to ensure that idtheme is an array of strings. Meanwhile, we are also checking if there have been any updates in type parsing.

LuisOP•5/29/25, 4:49 PM

Yes, it's an object in flow #222665, but if you check the response setting of CQthemes is an array in the original workflow.
That hasn't changed since the workflow was shipped and it has been working for 21 days

My workflow stopped working without modifying it

Similar Threads

Similar Threads

Similar Threads