Bug in test JSON parameters passed from startTrigger block

💬 Workflows
1

Goal: Building a workflow which starts off by stripping the "Limited", "Plc", etc. from a company name

Method: Data passed from startTrigger block is parsed using Regex and JS.

Expectation:

  • "A H Worth Limited" is passed from the startTrigger block
  • This is processed to strip " Limited"
  • "A H Worth" is returned

Reality:

  • Depending on the mood of the universe, random parts of the company name are passed from the startTrigger block, e.g. "A H Worth Limi"
  • "A H Worth Limi" is passed through as is because it doesn't match the criteria

screenshot 2025-07-15 at 09.32.55@2x
screenshot 2025-07-15 at 09.32.55@2x1634×852 107 KB

2

Sometimes the startTrigger is stale. From the overflow menu on the cleanCompanyName block, choose to run with previous blocks. This will make the startTrigger refresh.

Also, I see you are doing a lot of validation, might I suggest Valibot?

1 Like
3

Thanks for the recommendation @khill-fbmc . It will get me through this.

I type fast, but not that fast. I would expect the editor to catchup in the time I've finished typing and moused over to run my next block. Not for it to be stale :sweat_smile:

Retool, what's going on :thinking:

4

Hi @ferret141,

That is very odd. I am guessing you have made changes and then used the "deploy" button to lock in and save the contexts of blocks, correct?

Test JSON params can be buggy at best, our best practices recommend just using it when you are in early stages of prototyping and then removing them once you no longer need to test out dummy data.