Replace String Node throwing error

Original message was deleted

AI Support•9/13/24, 2:19 PM

AI Support Bot Information

@791353343426953246 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•9/13/24, 2:19 PM

AI Response

The error "Cannot read properties of undefined (reading 'replace')" usually indicates that the input string for the Replace String utility node is either

undefined

undefined

null

null

.

Here are some steps you can take to resolve this issue:

Ensure Input is Defined: Make sure the input string to the Replace String utility node is always defined and not
```
undefined
```
```
undefined
```
or
```
null
```
```
null
```
. You can add checks before this node to ensure the inputs are valid.
**Default Values**: Consider providing default values for the inputs if they are missing. This can prevent the node from failing. For instance:
- Use the If ElseIf Else node to check if the string is defined and non-null before passing it to the Replace String utility node.
- Set a default value using the DefaultDefault node.
Debugging: Add logging nodes before the Replace String utility node to log the input values. This will help you identify if the input is undefined or null when the entire workflow runs.
Empty Strings: Ensure that the input string is not an empty string if that is not the desired behavior. You might want to handle empty strings differently by adding conditions or checks.

For more information on handling nodes in BuildShip, you can refer to the following documentation:

Node Inputs
If Else Node
Set Default Values in Node Inputs【4:11†source】【4:18†source】.

Implementing these suggestions should help resolve the error. If you continue to experience issues, please send a support request via the in-app support.

BuildShip AI Support

•

9/13/24, 2:19 PM