When performing bulk actions, such as updating or reassigning multiple tasks at once, you may occasionally encounter an error stating that the action failed or rate limits were exceeded. This can happen even if you retry with a very small batch or a single task immediately afterward.

Why This Happens

• Per-Task Request Volume: In views like All Tasks, bulk updates send individual API requests for each task selected rather than a single batched call. Selecting a large number of tasks can trigger Rocketlane’s per-minute request limit (up to 100 requests per minute per user/endpoint).
• Rolling Window & Retry Blocking: The rate-limiting window runs for 60 seconds from your first request. Because failed/rejected attempts also count toward the rate limit, trying to re-run the action immediately—even on just 1 task—will continue to trigger the error until the full minute expires.
• Partial Success: The error message often surfaces due to underlying read or fetch limits during the process, even if the actual update/write requests succeeded.

Recommended Solutions & Best Practices

• Batch Your Updates: Reassign or update items in batches of 75 tasks or fewer at a time.
• Wait Between Batches: Allow at least 60 seconds between each bulk operation to allow the per-minute request limit to reset.
• Refresh First: Before retrying a failed update, refresh your browser page. In many cases, the updates were successfully saved despite the notification.

Bulk Update Limits by Feature

• Projects Bulk Update: Up to 1,000 projects can be updated at once.
• Tasks Bulk Update: There is no fixed maximum count limit published for task bulk updates, but operations are governed by the per-minute API request limit (100 requests/minute).