Events Showing as "Blocked" Status

Introduction

When events show as "blocked" in your ServerTrack logs, it means the events were rejected before being sent to platforms. This guide explains why events are blocked, how to identify the cause, and how to resolve blocked events.

What is "Blocked" Status?

"Blocked" status means an event was rejected by ServerTrack before processing. Blocked events:

• Are not sent to any platforms
• Are logged with the reason for blocking
• Cannot be retried (they're permanently blocked)
• Need the underlying issue fixed before events will succeed

Common Block Reasons

1. Validation Errors

Symptoms: Events blocked with "Validation Failed" message.

Causes:

• Invalid event name or format
• Missing required parameters
• Invalid data types (e.g., string instead of number)
• Malformed payload structure

Solution:

• Check Event Logs for specific validation error message
• Review the event payload to identify invalid data
• Fix the payload structure according to ServerTrack requirements
• Resend the event with corrected payload

2. Server Paused

Symptoms: Events blocked with "Server Paused" message.

Causes:

• Server Deck status is set to "paused"
• Service was suspended due to billing issues
• Service was manually paused
• Account expired beyond grace period

Solution:

• Go to Server Deck settings
• Check Server Deck status
• Resume service if paused
• Resolve billing issues if service suspended
• Check invoice status and payment methods

3. Limit Exceeded

Symptoms: Events blocked with "Limit Exceeded" message.

Causes:

• Monthly event limit reached
• Grace period (1,000 events) also exceeded
• Plan limit exceeded

Solution:

• Check current usage vs plan limit
• Wait for next billing cycle (limits reset monthly)
• Upgrade to a higher plan if consistently exceeding limits
• Monitor usage to prevent future overages

4. Invalid Authentication Key

Symptoms: Events blocked because authentication key is invalid or missing.

Causes:

• Authentication key missing from request
• Authentication key doesn't match any Server Deck
• Key was regenerated but script not updated

Solution:

• Verify authentication key in tracking script
• Compare key with ServerTrack dashboard
• Update script with correct key if needed
• Ensure key is included in all tracking requests

Checking Blocked Events

1. Check Event Logs

• Go to Event Logs in your ServerTrack dashboard
• Filter by "Blocked" status
• Review blocked events
• Check the "Response Message" column for block reason

2. Review Event Details

• Click on a blocked event to view details
• Review the event payload
• Check the response message for specific error
• Note the timestamp to identify patterns

3. Identify Patterns

• Are all events blocked, or just specific ones?
• Is it a specific event type that's blocked?
• Did blocking start after a recent change?
• Is blocking consistent or intermittent?

Fixing Blocked Events

Fix 1: Validation Errors

• Read the validation error message carefully
• Identify which field or parameter is invalid
• Check ServerTrack documentation for correct format
• Update your tracking code to send valid payloads
• Test with a simple event to verify fix

Fix 2: Server Paused

• Go to Server Deck settings
• If status shows "Paused", click "Resume" or "Activate"
• If paused due to billing, resolve payment issues
• Check invoice status and ensure invoices are paid
• Contact support if service won't resume

Fix 3: Limit Exceeded

• Check your current usage in dashboard
• Compare with your plan limit
• If at or over limit:
  • Wait for next billing cycle (limits reset)
  • Upgrade to higher plan
  • Reduce event volume if possible
• Monitor usage to prevent future overages

Fix 4: Invalid Authentication Key

• Get correct authentication key from dashboard
• Update tracking script with correct key
• Ensure key is included in all tracking requests
• Clear browser cache and test
• Verify events are no longer blocked

Preventing Blocked Events

1. Validate Payloads Before Sending

• Ensure all required parameters are included
• Verify data types are correct
• Check event names match ServerTrack requirements
• Test with sample events before production

2. Monitor Server Deck Status

• Regularly check Server Deck status
• Monitor billing and invoice status
• Set up usage alerts if available
• Keep payment methods up to date

3. Track Usage Regularly

• Monitor event usage vs plan limits
• Set alerts for approaching limits
• Plan for traffic spikes
• Upgrade plan proactively if needed

4. Keep Authentication Keys Updated

• If regenerating keys, update scripts immediately
• Document where tracking scripts are installed
• Test after updating keys
• Monitor for authentication errors

Blocked vs Failed Events

Important distinction:

• Blocked: Event rejected before processing (not sent to platforms)
  • Validation errors
  • Server paused
  • Limit exceeded
  • Invalid authentication
• Failed: Event sent to platforms but delivery failed
  • Platform authentication errors
  • Network issues
  • Platform API errors
  • Rate limiting (temporary)

Blocked events need the underlying issue fixed. Failed events are automatically retried.

Troubleshooting Checklist

When to Contact Support

Contact ServerTrack support if:

• Events remain blocked after fixing identified issues
• Server Deck won't resume from paused status
• You need help understanding validation errors
• Usage seems incorrect or limits not resetting
• You're seeing unexpected blocking behavior

Summary

Events are blocked when:

• Payload validation fails (invalid format, missing parameters, wrong data types)
• Server Deck is paused (manual pause, billing suspension, expired account)
• Event limit exceeded (plan limit + grace period exceeded)
• Authentication key is invalid or missing

To fix blocked events:

• Check Event Logs for specific block reason
• Fix the underlying issue (validation, status, limit, key)
• Verify Server Deck status is Active
• Ensure usage is within plan limits
• Test with new events to confirm fix

Blocked events are not sent to platforms and need to be fixed before events will process successfully.

For more information, see our Server Paused Guide, Event Limits Guide, and Authentication Key Errors.