# Maximum per-second limit: Impact to entire workflow?

**URL:** <https://forums.losant.com/t/maximum-per-second-limit-impact-to-entire-workflow/3520>\
**Category:** Help\
**Tags:** workflow\
**Created:** [January 10, 2021, 3:53pm UTC](https://forums.losant.com/t/maximum-per-second-limit-impact-to-entire-workflow/3520 "2021-01-10T15:53:47Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_Murdy](https://avatars.discourse-cdn.com/v4/letter/m/c57346/32.png) [@Michael\_Murdy](https://forums.losant.com/u/Michael_Murdy)\
**Post date:** [January 10, 2021, 3:53pm UTC](https://forums.losant.com/t/maximum-per-second-limit-impact-to-entire-workflow/3520/1 "2021-01-10T15:53:47Z")

</div>

I am working on a workflow that will run on a schedule (say weekly) that will loop over our active sales users and assign them access to the appropriate devices based on a device tag matching in a customer data table. As I am debugging this, I am getting a “maximum per-second limit reached error” in the debug panel. In the details, I see the “additional message received, but cannot be displayed due to high volume”.

My question is whether this message only pertains to displaying messages in the debug panel or if it impacts the workflow’s ability to complete.

If it is impacting the entire workflow, I presume adding a delay within the loop should allow this workflow to complete.

Please advise.

---

<div class="post-metadata">

**Author:** ![Brandon\_Cannaday](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/brandon_cannaday/32/14_2.png) [@Brandon\_Cannaday](https://forums.losant.com/u/Brandon_Cannaday)\
**Post date:** [January 10, 2021, 6:13pm UTC](https://forums.losant.com/t/maximum-per-second-limit-impact-to-entire-workflow/3520/3 "2021-01-10T18:13:23Z")

</div>

This only applies to the _display_ of the debug message. The underlying logic is still executed.

It’s common to see this message when using Debug Nodes in loops. A loop can execute extremely fast and potentially generate hundreds or thousands of debug messages in a very short period of time.

---

<div class="post-metadata">

**Author:** ![Michael\_Murdy](https://avatars.discourse-cdn.com/v4/letter/m/c57346/32.png) [@Michael\_Murdy](https://forums.losant.com/u/Michael_Murdy)\
**Post date:** [January 11, 2021, 7:14pm UTC](https://forums.losant.com/t/maximum-per-second-limit-impact-to-entire-workflow/3520/5 "2021-01-11T19:14:06Z")

</div>

Thanks for the quick clarification on this @Brandon_Cannaday!

---

<div class="post-metadata">

**Author:** ![ruba\_jabal](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/ruba_jabal/32/4251_2.png) [@ruba\_jabal](https://forums.losant.com/u/ruba_jabal)\
**Post date:** [February 12, 2023, 1:36pm UTC](https://forums.losant.com/t/maximum-per-second-limit-impact-to-entire-workflow/3520/8 "2023-02-12T13:36:41Z")

</div>

> [@Brandon\_Cannaday](#):
>
> This only applies to the _display_ of the debug message. The underlying logic is still executed.

I have similar concern as I receive the same message when updating device attributes value using loop. I assume that the device attributes state are still updated however it can’t be displayed in the debug panel. right?

---

<div class="post-metadata">

**Author:** ![Brandon\_Cannaday](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/brandon_cannaday/32/14_2.png) [@Brandon\_Cannaday](https://forums.losant.com/u/Brandon_Cannaday)\
**Post date:** [February 12, 2023, 8:28pm UTC](https://forums.losant.com/t/maximum-per-second-limit-impact-to-entire-workflow/3520/9 "2023-02-12T20:28:41Z")

</div>

Correct. Your attributes are still being updated correctly. We’re only limiting how many debug messages are sent to the browser - we’re not stopping or limiting the underlying workflow.