Error G504

Error G504 - Gateway Timeout

What This Means

The NR Waste Plus application took too long to respond to your request and the connection timed out. This happens when the system is working on your request but can't complete it within the expected time. Think of it like being on hold with customer service for so long that the call disconnects - the system was trying to help you, but it took too long.

Why This Happens

This error occurs when:

• Complex operations: You're performing an action that requires a lot of data processing or calculation
• Large data requests: Trying to load or export very large amounts of information
• System slowness: The application is running slower than usual due to high usage or technical issues
• Heavy database operations: The system is searching through or updating large amounts of data
• Network delays: Slow communication between different parts of our system

What You Can Do

1. Try again: Often the request will work on a second attempt
2. Simplify your request: If you were requesting a large report or searching for lots of data, try:
   • Breaking it into smaller pieces
   • Narrowing your search criteria
   • Selecting a shorter date range
   • Reducing the number of items you're working with at once
3. Try during off-peak hours: If possible, attempt the same action during less busy times of day
4. Wait before retrying: Give the system a minute or two before trying again
5. Save your work: If you were entering data, keep a copy of what you entered so you don't lose it

When to Contact Support

You should reach out to the support team if:

• This error happens repeatedly for the same action, even with simplified requests
• The timeout occurs on routine operations that normally complete quickly
• You're unable to complete essential work due to persistent timeouts
• The error started happening suddenly when it worked fine before
• You're the only one experiencing this while colleagues can complete the same actions

When contacting support, please provide:

• What specific action you were trying to perform
• How much data you were working with (e.g., date ranges, number of records)
• Whether this action worked successfully for you in the past
• The exact time the timeout occurred
• Whether simplifying the request helped or not
• Any filters or search criteria you were using