Running on Monday.com?

Monday automations failing or boards sluggish? We ship it properly.

Monday.com looks like a spreadsheet and runs on a graph. That is why a renamed column breaks an automation you forgot about, a GraphQL mutation returns 429 halfway through a board duplicate, or a dashboard chart suddenly totals a status that no longer exists. We rebuild the automations against current columns, apply backoff to the API client, and bring the integrations back online.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

monday-graphql.log

still misfiring

What it is

Monday.com at a glance

Monday.com is a work operating system founded in 2012 by Roy Mann, Eran Kampf and Eran Zinman in Tel Aviv. It presents work as colorful boards where each row is an item and each column is a typed field, with views (table, timeline, kanban, calendar, chart) overlaid on top. The product grew from a simple team tracker into a platform used for CRM, project delivery, HR, operations and software development.

The platform offers workspaces, boards, items, subitems, groups, columns (status, number, person, date, timeline, mirror, formula, dropdown, link), views, dashboards, docs, forms, automations (if-this-then-that recipes) and apps. The developer platform exposes a GraphQL API with complexity-based rate limiting, webhooks, OAuth and the monday-apps CLI for building and publishing apps to the Marketplace. The issues we see cluster around three things: automation recipes that break silently when columns are renamed or statuses are changed, GraphQL queries that exceed the complexity budget on large boards, and the mirror and formula columns that slow a board to a crawl once item count climbs.

Type
Work operating system and project management platform
First released
2014, publicly as dapulse
License
Proprietary SaaS, per-seat pricing with Free, Basic, Standard, Pro and Enterprise tiers
Maintained by
monday.com Ltd.
Typically used for
Project management, CRM, operations, HR workflows, custom business applications

The honest version

Monday.com pros and cons

No technology is all upside. This is where Monday.com earns its place and where it tends to cause trouble.

Where Monday.com is strong

  • Approachable to non-engineersBoards look like spreadsheets, so finance, operations and marketing teams pick it up in an afternoon without an onboarding deck.
  • Typed columns beat generic cellsStatus, person, date, timeline, number and formula columns carry meaning, so automations and dashboards can reason about the data instead of parsing strings.
  • Automations handle routine glueThe recipe builder covers status changes, assignments, notifications and dates without a Zapier bill, which is what keeps light workflows out of engineering.
  • Dashboards aggregate across boardsNumber widgets, charts and portfolio views can pull from several boards, which lets a leadership team look across teams without a separate BI tool.
  • Apps Framework for real extensibilityTeams can build their own board views, item cards, integrations and custom actions, and publish them to the Marketplace or install privately. The platform is a build surface, not just a product.
  • GraphQL API with webhooksThe API is well documented, mutations are atomic, and webhooks cover most lifecycle events, which makes integrations with CRM, finance and engineering tooling feasible.

Where Monday.com bites

  • Complexity-based rate limits catch bulk workThe GraphQL API charges requests against a per-minute complexity budget, and a naive query that pulls items with their columns can exhaust the budget in seconds, failing a bulk job partway through.
  • Automations break when columns changeRename a status, change a column type or delete a column, and automations referencing it fail silently. Nothing enforces a review, and workspaces accumulate broken recipes.
  • Mirror and formula columns are expensiveBoards with many mirror columns, especially ones that chain across three or four boards, slow to a crawl above a few thousand items. The feature is powerful on paper and painful in practice at scale.
  • Per-seat pricing with a minimumThe lower tiers have a three-seat minimum, and Pro and Enterprise rates climb fast. Teams who add a handful of occasional contributors see the bill jump more than they expected.
  • Permissions are shallowBoard-level and workspace-level permissions do not reach into per-column access, so a board that contains both public and sensitive data usually has to be split into two.
  • GraphQL deprecations are a running taskThe API has been reshaped several times (items_page replacing board.items, limits moving from calls to complexity), and integrations that were written two years ago need periodic rework to stay compatible.

Sound familiar?

Common Monday.com problems we fix

The Monday.com problems that bring people to us, and what you have once each one is fixed.

ComplexityException: exceeds 5000000

GraphQL queries exceed the complexity budget

A query that asks for items and their column_values and their subitems and their assets all at once, exceeding the per-request complexity cap. The request fails outright.

Queries paginated and budgeted

automation skipped: column renamed

Automations break after a column rename

A status column renamed by a well-meaning admin, with recipes that reference it by name silently failing. Status transitions no longer trigger notifications and nobody notices until a deadline slips.

Automations bound to current columns

429 complexity budget exceeded

Bulk imports throttle out

An API client without backoff firing mutations as fast as it can, blowing through the per-minute complexity budget inside a minute. The import halts and leaves the board half-populated.

Import paced, resumable

mirror column slow on 8200 items

A board becomes unusably slow

Mirror columns pulling values from large source boards, or formula columns recomputing on every edit, dragging page loads past twenty seconds. The team starts avoiding the board rather than opening it.

Columns optimised, cache strategy agreed

deprecation: board.items

An old integration stops working after API updates

A client written against board.items that hit the deprecation date and now returns errors. The fix is a migration to items_page with cursor pagination, not a config change.

API client on current endpoints

webhook delivery failed, 504

Webhook consumer is timing out

A consumer that does too much work inside the webhook handler and returns 504 to Monday, triggering retries that compound the problem. Events are lost after the retry budget runs out.

Handler responds fast, work queued

column_values JSON malformed for 'date'

Mutations fail with column_values errors

A client writing a date column with a plain string rather than the JSON structure Monday expects, or a status column with the wrong index. Every mutation fails with a vague 400.

Column payloads correct per type

SCIM duplicate email

SCIM provisioning fails for some users

Users present in two IdP groups both syncing to Monday, triggering duplicate email errors. New hires hang in a pending state until the IdP side is deduplicated.

SCIM mapping clean

What we do

Monday.com help, board to app

Call us for one broken automation, or let us own the whole Monday workspace and app surface.

Rescue
A board that will not load, automations breaking silently after a column change, or a GraphQL job failing with complexity errors. We stabilise the workspace first and explain the cause second.
Workspace design
Board structures per team, column conventions and group naming agreed, and mirror and formula usage kept within performance limits.
Automation audit
Recipes inventoried against current columns, overlapping rules consolidated, and a review cadence that keeps new automations from sprawling.
GraphQL API integrations
Custom webhooks, warehouse exports, migrations and third-party syncs that respect the complexity budget, handle pagination correctly, and survive API deprecations.
Apps Framework development
Custom board views, item card widgets, integrations and workflow actions built and published through the monday-apps CLI, with the OAuth and signing details handled.
Managed Tech
Monthly automation and API integration reviews, Apps Framework release monitoring, column-performance checks, and an engineer on call when a GraphQL deprecation lands mid-week.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Monday.com alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Monday.com questions

Something else? Call+1 737 727 7327

Why does our Monday.com GraphQL API keep hitting complexity errors?

Because the complexity score for a request multiplies by nested fields: fetching items pulls them, fetching their column_values multiplies by the number of columns, and asking for subitems and assets in the same call compounds the score further. We rewrite the query to paginate items_page, request only the columns actually needed, and split the mutations into batched chunks that each stay under the per-minute budget.

How do we stop automations from breaking when we rename columns?

By making column rename a reviewed action rather than a casual admin task, and by binding automation recipes to columns through stable identifiers where the UI allows it. We also inventory the existing recipes before any rename so the ones that reference the old name can be updated in the same change, and we add a smoke test that triggers each recipe after the rename lands.

Why is our Monday board loading so slowly?

The usual culprits are mirror columns pulling from large source boards, formula columns recomputing on every edit, and a board that has grown past a few thousand items with many views open. We identify which columns are expensive, replace mirrors with imports where appropriate, and often recommend splitting the board along meaningful boundaries once it has grown past comfortable limits.

Can we build a custom Monday app for our internal workflow?

Yes. The Apps Framework supports board views, item card widgets, integration recipes and custom automation actions, all deployed through the monday-apps CLI. Common builds are approval flows, internal CRM panels, Salesforce or HubSpot sync and reporting views that pull from the warehouse. We design, build, publish through the Marketplace or install privately, and keep them current across API changes.

How do we handle Monday.com GraphQL deprecations?

Watch the developer changelog, keep an inventory of the queries and mutations each integration uses, and rework them before the deprecation date rather than on the day. items_page replacing board.items is the most recent large change; the pattern is the same each time, which is why a quarterly audit beats a rush to fix things when calls start failing in production.

How much does Monday.com help cost?

A quote is free. Share the plan tier, the workspace scale, and what is breaking, and we come back with a scope and a fixed price before anyone touches the account.

Free estimate

Monday.com giving you trouble?

Automation audits, GraphQL integrations, Apps Framework builds and workspace redesign. We work on the whole Monday surface, not one board at a time.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.