# Webhook 1000 subscription limitation for bidirection sync.

**URL:** <https://community.hubspot.com/t/webhook-1000-subscription-limitation-for-bidirection-sync/88010>\
**Category:** APIs & Integrations\
**Tags:** object, webhooks\
**Created:** [August 22, 2023, 9:40am UTC](https://community.hubspot.com/t/webhook-1000-subscription-limitation-for-bidirection-sync/88010 "2023-08-22T09:40:23Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Eric\_Goldman](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/eric_goldman/32/1048_2.png) [@Eric\_Goldman](https://community.hubspot.com/u/Eric_Goldman)\
**Post date:** [August 22, 2023, 11:33pm UTC](https://community.hubspot.com/t/webhook-1000-subscription-limitation-for-bidirection-sync/88010/4 "2023-08-22T23:33:23Z")

</div>

Hey @ArpitAtDock - happy to help!

With Workflows, the issues we’ve run into are two-fold:

1. Workflows not firing: A workflow might not fire on every event, especially on high-frequency events (i.e., an object moving through a set of statuses). It’s rare, but common enough to cause a sync to get broken.

2. Workflows being altered: Workflows can’t be managed programmatically, so key logic is outside your code/implementation. Workflows can be altered / hard to maintain as a result.

Ultimately, workflows felt like a bit of a hack that we wanted to avoid.

---

_[View the full topic](https://community.hubspot.com/t/webhook-1000-subscription-limitation-for-bidirection-sync/88010)._