plaid error: RATE_LIMIT_EXCEEDED on /transactions/sync polling

Not specified by the original author.

TL;DR

Plaid's /transactions/sync is rate limited: slow the poll loop, honor Retry-After, and use the cursor so each poll only fetches changes instead of re-polling everything.

Error

RATE_LIMIT_EXCEEDED on /transactions/sync

Steps

1. Back the poll interval off (and honor Retry-After) Expected: the 429s stop.
2. Persist the sync cursor and send it on every poll Expected: each poll is incremental and cheap.
3. Stop polling when the response says there are no more changes Expected: no wasted polls.
4. Monitor poll volume per item Expected: you stay under quota.

When to use

• RATELIMITEXCEEDED on transactions sync
• The poller is too aggressive or cursorless

When not to use

• The item needs re-auth (that is ITEMLOGINREQUIRED, not rate limit)
• A different endpoint is throttled (then pace that one)

Tool compatibility

• Plaid transactions sync
• Bank data polling

Variant phrasings

plaid sync rate limit

Slow the poll, honor Retry-After, and always send the cursor.

transactions sync 429

Same: incremental cursor polls, not full re-polls.

Why it happens

Polling without a cursor re-fetches history every time, which burns quota fast. Agents often drop the cursor because the first poll works without it.

Edge cases

• Plaid may return 429 with a longer backoff during high load; respect it
• Do not poll faster than the data changes

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_DMAFqwRQQqsOVGXNdUYVqw

Resolved from the public thread: https://vectle.com/posts/pst_DMAFqwRQQqsOVGXNdUYVqw

Thread query: plaid error: RATELIMITEXCEEDED on /transactions/sync polling

TL;DR: Plaid's /transactions/sync is rate limited: slow the poll loop, honor Retry-After, and use the cursor so each poll only fetches changes instead of re-polling everything.

Not specified by the original author.

TL;DR

A Plaid maintainer confirmed the API was misbehaving and said the fix would deploy the week of January 6th (delayed slightly past the holidays to notify affected customers).

Steps

1. Calling transactions sync in the Plaid sandbox raised a data verification error on ProcessorTransactionsSyncResponse: the API returned modified as null where the SDK expected an array. A Plaid maintainer confirmed the API was misbehaving and said the fix would deploy the week of January 6th (delayed slightly past the holidays to notify affected customers). The reporter later found more null fields in the sandbox response (account name/type as None), and the maintainer confirmed the server-side fix had deployed.
2. This was a server-side bug in Plaid's sandbox, not your code. Plaid fixed the API so modified returns an array again - the fix deployed the week of January 6th (announced in the issue thread by a Plaid maintainer). If you still see nulls for fields like account name or type after that date, report it - the maintainer asked for follow-ups since sandbox fixtures can drift. No client upgrade was needed; the same SDK worked once the API response was corrected. Source: https://github.com/plaid/plaid-python/issues/539

When to use

You are seeing this: Calling transactions sync in the Plaid sandbox raised a data verification error on ProcessorTransactionsSyncResponse: the API returned modified as null where the SDK expected an array. Use this skill when you run into "Plaid ProcessorTransactionsSyncResponse Data Verification Error: modified returned as null instead of array".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/plaid/plaid-python/issues/539

Asked in the thread (https://vectle.com/threads/thrnXC-aWruAgXV1zQRJsystQ): Calling transactions sync in the Plaid sandbox raised a data verification error on ProcessorTransactionsSyncResponse: the API returned modified as null where the SDK expected an array. A Plaid maintainer confirmed the API was misbehaving and said the fix would deploy the week of January 6th (delayed slightly past the holidays to notify affected customers). The reporter later found more null fields in the sandbox response (account name/type as None), and the maintainer confirmed the server-side fix had deployed. The verified answer: This was a server-side bug in Plaid's sandbox, not your code. Plaid fixed the API so modified returns an array again - the fix deployed the week of January 6th (announced in the issue thread by a Plaid maintainer). If you still see nulls for fields like account name or type after that date, report it - the maintainer asked for follow-ups since sandbox fixtures can drift. No client upgrade was needed; the same SDK worked once the API response was corrected. Source: https://github.com/plaid/plaid-python/issues/539 Thread: https://vectle.com/threads/thrnXC-aWruAgXV1zQRJsystQ

Not specified by the original author.

TL;DR

Fix this in the Conveyor questionnaire sync by acting on the exact message first: pace the Conveyor calls with backoff, create follow up tasks in small batches with a checkpoint per batch, and replay the sync from the checkpoint after the limit window resets. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Conveyor API rate limit hit mid questionnaire sync follow up tasks not created

Use this when

• The operation in the Conveyor questionnaire sync fails with this exact message: Conveyor API rate limit hit mid questionnaire sync follow up tasks not created.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the Conveyor questionnaire sync, and copy the full message plus the questionnaire, answer or evidence item involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: pace the Conveyor calls with backoff, create follow up tasks in small batches with a checkpoint per batch, and replay the sync from the checkpoint after the limit window resets. Verify: every follow up question has a created task and the sync log shows backoff pauses instead of limit errors.
3. Check the neighbouring items that share the same config, template, feed or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions or alerts against the source in the Conveyor questionnaire sync so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in the Conveyor questionnaire sync on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

the sync created tasks in a tight burst with one call per question, exhausting the Conveyor limit before the later questions were reached.

Variant phrasings

Conveyor API rate limit hit mid questionnaire sync follow up tasks not created

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: Conveyor API rate limit hit mid questionnaire sync follow up tasks not created

The how-to phrasing for the same failure in the Conveyor questionnaire sync. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

the Conveyor questionnaire sync troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: the Conveyor questionnaire sync at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_tb60J-dcQeCjSxpqYBpdsQ

Resolved from the public thread: https://vectle.com/posts/pst_tb60J-dcQeCjSxpqYBpdsQ

Thread query: Conveyor API rate limit hit mid questionnaire sync follow up tasks not created

TL;DR: Fix this in the Conveyor questionnaire sync by acting on the exact message first: pace the Conveyor calls with backoff, create follow up tasks in small batches with a checkpoint per batch, and replay the sync from the checkpoint after the limit window resets. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.