Skip to main content

Understanding Mass Delete Timeouts and Session Impact (CRM)

When performing large mass delete operations in Dazos CRM, you may experience 504 Gateway timeout errors. This article explains the scope of these timeouts and how they affect user sessions across your organization.

When to Use / Why It Matters

Understanding timeout behavior is crucial when planning mass delete operations, especially during business hours. This knowledge helps administrators:

  • Plan mass deletions with minimal disruption to team productivity

  • Communicate realistic expectations to users about system availability

  • Implement workarounds when large operations are necessary

How Mass Delete Timeouts Work

Session Impact Scope

When a mass delete operation causes a 504 Gateway timeout, the impact is limited to a specific scope:

  • Affected: Only the user session that initiated the mass delete operation

  • Not Affected: All other users on different devices and sessions

  • System Status: The CRM system remains fully operational for other users

What Happens During a Timeout

The user who initiated the mass delete will experience:

  • 504 Gateway error messages when trying to access CRM pages

  • Inability to navigate or perform actions until the process completes

  • Temporary loss of access to their current session

Meanwhile, the mass delete operation continues running in the background until completion.

Workaround Options

If you need to continue working while a mass delete operation is in progress, you have several options:

For the Affected User

  • Private Browser Window: Open an incognito/private browsing window and log in again

  • Different Browser: Use a different web browser to access the CRM

  • Different Device: Log in from another computer, tablet, or mobile device

For Other Users

Other team members can continue using the CRM normally without any interruption or performance impact.

Tips & Notes

💡 Planning Tip: Schedule large mass delete operations during off-hours or low-usage periods when possible.

⚠️ Important: Do not attempt to stop or cancel a mass delete operation once it has started, as this could result in incomplete data removal.

Best Practice: Inform your team before performing large-scale deletions so they understand any temporary access limitations.

Related Resources

  • How to Restore Data from the Recycle Bin (CRM)

  • Session Expired — "Click here to Log In Again" Message Persists (CRM)

Did this answer your question?