[DONE] Request Header Fields Too Large

🔧 Bugs & Issues
1

Got this in a relatively small table (22 records).

image

The automation from my perspective is a simple one - I want to change a relationship field automatically for those 22 records. It should look up the linked company, then search for the client briefing record for that company and link it with the record. See the flow:

image
image660×884 42.8 KB

I don’t think the issue is related to the automation?

Update: When I limited the search result to 1 (there is only one anyway) it started to work. But it should have also worked without this?

2 Likes
2

Hi @dirk_s,

Thanks a lot for sharing this and for the detailed description!

We haven’t encountered this specific error before, so it’s great that you found a workaround for now. However, we’d love to better understand the root cause to make sure it doesn’t happen again — either for you or others.

Would it be possible for you to grant us temporary access to the relevant workspace? That would help us a lot in reproducing the issue and investigating it in more detail.

Thanks again, and best regards,
Leo

1 Like
3

Hi @Leo yes, we will give you access later today. @Eric_Scherlich experienced the same issue in a totally different context and organisation today as well.

2 Likes
4

@Leo you are invited now.

1 Like
5

Great thanks for the support @dirk_s! We will analyze the problem today and give you an update.

Best regards
Leo

1 Like
6

@dirk_s the team is investigating the issue. Just a little follow up question: Did you encounter this issue in a normal run or a simulation run?

7

Hi, @Tim we experienced this in normal runs. We usually do not use simulated runs…

1 Like
8

Hello! I’m facing the same issue here. Any updates on the matter?

9

Hi @agnes.farias,

thanks for sharing - we have reached out via direct message to gather more info and work on a resolution.

Cheers
Tim

10

@Tim this is still happening. This time in a loop:

image
image1038×190 10.5 KB

11

Just one more thing to try for everyone experiencing this bug. In my case it might be related to a loop, where your search or collect stuff. I was of the opinion, that only the loop value was being worked on - but apparently the array grew bigger and bigger. Add a clear collected at the end of the loop, unless you want to build something big.

image
image1729×195 8.06 KB

3 Likes
12

Thanks for your persistance @dirk_s, @agnes.farias and @Eric_Scherlich.

Good news: The team was able to provide and deploy a fix over the weekend. This behaviour should no longer occur. :tada:

Some background info:

While this issue appeared rather mysterious at first, it was easy to reproduce after @dirk_s provided some additional info. Indeed, all it took was:

  • Collect records, e.g. via a search action without a limit and yield a result set larger than one, 10-20 was already enough
  • Use a search action, specify a relation field filter and provide the previously collected records as input to the relation filter UI

The second action would then produce the observed error. Under the hood, the issue was that the underlying logic would send the whole records collection as a filter input, instead of just using the IDs. This would indeed lead to an unexpectedly large request and the error.

Now, only IDs will be provided and also large collections should not lead to this error anymore.

Thanks for your patience & happy building :building_construction:
Tim

3 Likes