Why is Fetching Data causing a spike?

Hello all,

I know it’s D-Day and we’ll be migrated over to the new pricing today - YIKES!

My WLU have suddently gone up for no apparent reason - I prevented workflows runnings unless certain conditions where met which reduced it massively. But now I’ve got this ‘Fetching Data’ issue which I can’t drill down into.

How can I search what is causing these searches please?

Thank you

Find out where you’re making all those searches.

Optimize your flow.

Ideally you want to search for your items once (load it in your page somewhere) then refer to that ‘loaded’ data. Otherwise you’re “re-searching” multiple times per load.

Same applies in hard-code:

<html>
<head>
<some awesome script that loads data>
</head>
<body>
<SessionProvider data={data}>
<content /> - here is where we can refer to that data at any point within context of the app.
</SessionProvider>
</body>
</html>

This is not a functional code, just an example.

Hmm, I wonder if adding Hotjar script to the header has anything to do with it.

Probably not. It’s clearly your data-searching according to your image.

How do you think I may be able to track it down?
I can’t click on the Fatching Data to drill down any further.

Im also really confused as it’s all on version-test and not on dev although dev is latest update.

Thanks for any advice.

That is strange usually it lets you click it and see the sources…

Hi there! Our Support team is happy to address questions about pricing and workload, please visit our Support Center, where you can explore articles on pricing, billing, and workload topics or connect with a member of our Support team. To reach live support, simply open the chatbot and request to speak with our team.

If I click on Featching Data it just shows Individual Data Request as 100% and then I can’t click on anything else (I know sometimes it takes you to the workflow etc).

So I have absolutely no idea how to start tracking the source of this 250 searches a minute consumption :confused:

1 Like

In my experience, Individual Data Request typically refers to pulling up data by it’s UID, either through a search, or an API request. An API request fetching 250 items by UID only is very WU light, but will show up as at least 250 searches and ‘Individual Data request’ on the chart.

How much WU usage are you seeing minute by minute with this? Do you have any APIs calling data?

1 Like

There’s absolutely nothing going on with the app - no users, no backend workflows running etc. And I’m seeing 10 WLU units a minute - while it doesn’t seem much, 600 per hour/14400 a day for nothing and my allowance is soon going to be eaten up.

I can’t see any logs which confuses me.

I made a save point and deleted a few things. Nothing changed so rolled back and now some repeating groups have errors as they’re looking for completely different data.

When you enable all log types and search the logs, what do you see?

Absolutely nothing!

This is what’s confusing me!

The only logs I see are if I start doing things which causes workflows to execute. I just searched back 2, 10, 20 minutes ago and nothing. But searching back 30 minutes ago I see the workflows that I initiated. So they are displaying, but not when the site is idle and yet still generating WLU consumption.

Are you sure you enabled the HTTP request output checkboxes?

As mentioned individual data requests are just that, single data requests for a Thing.

Plugins. Any plugins running in the page?

All boxes ticked:

I do have some plug ins, but I can’t identify which page is causing this WLU consumption with no server logs or being able to click any further than Individual Data Request to take me to the workflow or page.

This issue has only just started happening and the past 24h has seen the following (mostly while idle, only me testing):

It’s the difference between Dev and Live which I’m confused about too:

Could be a privacy rules issue in dev… Are you using a dev user account that has access to all fields of multiple data types? That could be causing larger data returns in dev.

This topic was automatically closed after 70 days. New replies are no longer allowed.