B A C Docs
Console
Error Codes & Troubleshooting Directory
8 min read read

Error Codes & Troubleshooting Directory

Complete catalog of B A C enterprise error codes (BAC-ERR-XXX-YYY), root causes, step-by-step resolution guides, and self-service diagnostics.

Official Directory 20+ Standardized Error Codes

B A C Enterprise Error Code Taxonomy

Whenever an operation encounters a friction point in the Client Dashboard, Ingress Routing, or Runtime Containers, a unique standardized error code is generated. Reference this directory for verified root causes, instant fixes, or to raise a prioritized engineering ticket.

Open Support Hub
Showing all 20 verified error codes
BAC-ERR-AUTH-101 Medium Severity Authentication
Raise Ticket

Client Session Expired or Token Invalid

Your authenticated browser session or JWT bearer token has expired, been revoked, or is mathematically invalid.

Primary Root Causes
  • Inactivity beyond the 24-hour security session threshold
  • Password or 2FA security credentials recently modified on another device
  • Corrupted browser cookie or cross-site token mismatch
Step-by-Step Resolution Guide
  1. Click the "Login Again" button to re-authenticate with your verified email and password.
  2. Clear your browser cookies for officialbac.in if you experience repeated session drops.
  3. If you have 2FA enabled, ensure your authenticator TOTP code is entered within the 30-second window.
Proactive Prevention: Keep "Remember Me" checked on trusted work devices and maintain accurate time sync on your 2FA authenticator app.
BAC-ERR-AUTH-102 Medium Severity Authentication
Raise Ticket

Two-Factor Authentication (2FA) Code Invalid or Expired

The submitted 6-digit TOTP verification code does not match the cryptographic secret key or was submitted after the time slot expired.

Primary Root Causes
  • Device clock out of sync with international NTP time servers
  • Entered an expired 30-second TOTP token
  • Mismatched authenticator profile (e.g. Google Authenticator vs. Authy)
Step-by-Step Resolution Guide
  1. Check your device settings and ensure "Set Time Automatically" is enabled.
  2. Wait for the authenticator app code to refresh and enter the fresh 6-digit code immediately.
  3. Use one of your 8-digit Emergency Backup Recovery Codes if your device is unavailable.
Proactive Prevention: Store your emergency recovery codes in a safe offline password manager.
BAC-ERR-AUTH-103 High Severity Authentication
Raise Ticket

Invalid Credentials or Verification Block

The email address and password combination failed authentication or triggered rate-limiting safeguards.

Primary Root Causes
  • Incorrect password entered multiple times
  • Temporary IP rate-limiting active due to rapid consecutive attempts
  • Account pending email verification confirmation
Step-by-Step Resolution Guide
  1. Double check caps lock and keyboard layout, then re-enter your password.
  2. Click "Forgot Password" to receive a secure password reset link on your registered email.
  3. Wait 5 minutes for the automated rate-limit window to reset.
Proactive Prevention: Use a trusted password manager to avoid typos.
BAC-ERR-AUTH-104 Critical Severity Security
Raise Ticket

Account Suspended or Under Compliance Review

Your account has been placed under administrative restriction or compliance verification.

Primary Root Causes
  • Unpaid invoice or depleted fuel tank credits beyond the grace period
  • Security anomaly or violation of Terms of Service detected
  • Pending statutory DPDP or identity verification
Step-by-Step Resolution Guide
  1. Review your registered email inbox for compliance notifications from [email protected].
  2. Recharge your Fuel Tank balance if account suspension is due to billing arrears.
  3. Raise an urgent Critical priority ticket with your account ID for immediate squad review.
Proactive Prevention: Keep auto-recharge enabled on your Fuel Tank billing profile.
BAC-ERR-DEPLOY-201 High Severity Deployments
Raise Ticket

GitHub Repository Clone or Webhook Fetch Failed

The automated deployment pipeline could not clone or fetch the specified branch from your GitHub repository.

Primary Root Causes
  • B A C GitHub App lacks read permissions on private repository
  • The selected branch name was renamed or deleted on GitHub
  • GitHub API rate limits or transient GitHub service disruption
Step-by-Step Resolution Guide
  1. Visit your GitHub Account Settings -> Applications -> B A C Deployments and ensure repository access is granted.
  2. Verify that the branch name specified in your Service Configuration matches your GitHub repository.
  3. Trigger a manual "Redeploy Now" from your App Detail overview page.
Proactive Prevention: Keep repository permissions set to "All Repositories" or explicitly include newly created web services.
BAC-ERR-DEPLOY-202 High Severity Deployments
Raise Ticket

Build Script Execution Timeout Exceeded (>180s)

The "npm run build" or compilation script took longer than the allocated 180 seconds threshold on the build runner.

Primary Root Causes
  • Heavy asset bundling, unoptimized media files, or large TypeScript compilation
  • Infinite build loop or hanging postinstall lifecycle script
  • Extensive unbundled node_modules dependencies
Step-by-Step Resolution Guide
  1. Optimize your build command (e.g. use "vite build" or "next build" with cache).
  2. Ensure no devDependencies or hanging processes (like long-running watchers) are triggered during build.
  3. Inspect build logs in the App Detail console to find the exact step where execution stalled.
Proactive Prevention: Test builds locally using "npm run build" before pushing commits to your production branch.
BAC-ERR-DEPLOY-203 High Severity Deployments
Raise Ticket

Missing Entrypoint File or Start Script

The runtime engine could not locate the entrypoint script (server.js, app.js, index.js) or "npm start" definition.

Primary Root Causes
  • package.json missing "scripts.start" command
  • Main entry file located in a subdirectory (e.g., /src/index.js) without configuring Root Directory
  • Incorrect casing in file naming (e.g. App.js on Linux vs. app.js on Windows)
Step-by-Step Resolution Guide
  1. Ensure your package.json has a valid "start" script, e.g. "scripts": { "start": "node server.js" }.
  2. If your backend is in a subfolder, set "Root Directory" in Service Configuration (e.g., "/backend" or "/server").
  3. Ensure standard lower-case entry file naming.
Proactive Prevention: Always provide a standard package.json start script for Node.js workloads.
BAC-ERR-DEPLOY-204 Medium Severity Deployments
Raise Ticket

Node.js Runtime Engine Version Mismatch

The application dependencies require a different Node.js engine version than the currently selected runtime environment.

Primary Root Causes
  • Project uses syntax or native addons requiring Node 20.x/22.x while configured on Node 16.x/18.x
  • "engines" field in package.json conflicts with the selected deployment runtime
Step-by-Step Resolution Guide
  1. Go to Service Configuration -> Runtime Engine in your Client Console.
  2. Select the matching Node.js version (Node 22.x LTS, Node 20.x LTS, or Node 18.x LTS).
  3. Save configuration and click "Redeploy Service".
Proactive Prevention: Match your production Node.js runtime version with your local development environment.
BAC-ERR-PROC-205 High Severity Process & Runtime
Raise Ticket

Port Binding Collision or Missing Dynamic PORT Env

The application hardcoded a static network port instead of listening to the dynamically assigned process.env.PORT.

Primary Root Causes
  • Server hardcoded to listen on "3000" or "8080" rather than process.env.PORT
  • Child process spawned on an unrouted port
Step-by-Step Resolution Guide
  1. Update your server listen code to: const port = process.env.PORT || 3000; app.listen(port, () => ...);
  2. Commit and push changes to trigger an automated hot reload.
  3. Check Console Logs to verify the application reports "Listening on port XXXX".
Proactive Prevention: Always read process.env.PORT in cloud deployment environments.
BAC-ERR-PROC-206 Critical Severity Process & Runtime
Raise Ticket

Process Out of Memory (OOM) / Heap Exhausted

The application process exceeded the allocated memory RAM threshold and was terminated by the container supervisor.

Primary Root Causes
  • Memory leak in caching layer, unclosed file descriptors, or recursive promises
  • Processing massive payloads in-memory without stream buffering
  • Service package RAM allocation insufficient for heavy traffic loads
Step-by-Step Resolution Guide
  1. Check your live Metrics tab in App Detail for RAM utilization spikes.
  2. Refactor large data operations to use Node.js streams instead of loading entire files into memory.
  3. Upgrade your instance tier or scale horizontally to a higher compute quota.
Proactive Prevention: Profile memory allocations locally with node --inspect and stream large data payloads.
BAC-ERR-PROC-207 High Severity Process & Runtime
Raise Ticket

Health Probe Timeout / 503 Maintenance Triggered

The regional edge ingress health checker failed to receive a 200 OK response on the configured health path within 10 seconds.

Primary Root Causes
  • Synchronous blocking operations on the Node.js event loop during initialization
  • Database connection failed or timed out during server boot
  • Custom health path configured to a protected or non-existent endpoint
Step-by-Step Resolution Guide
  1. Verify that your database URI (e.g. MongoDB Atlas / PostgreSQL) connects cleanly at startup.
  2. Ensure your health check route (e.g. GET / or GET /health) responds immediately with HTTP 200.
  3. Check Console Logs in the App Detail view for unhandled promise rejections.
Proactive Prevention: Implement lightweight, unauthenticated GET /health endpoints that return {"status":"ok"}.
BAC-ERR-BILL-301 High Severity Billing & Fuel Tank
Raise Ticket

Insufficient Fuel Tank Credits (< ₹10 Minimum Threshold)

Your account balance has depleted below the minimum compute operational reserve, placing services in conservation mode.

Primary Root Causes
  • Continuous hourly compute consumption exhausted prepaid credits
  • Auto-recharge disabled or payment method expired
  • High network bandwidth consumption exceeding credit reserve
Step-by-Step Resolution Guide
  1. Navigate to Client Dashboard -> Fuel Tank & Billing.
  2. Click "Recharge Fuel Tank" and add credits via UPI, Net Banking, or Credit/Debit Card.
  3. Once recharged, your services will automatically reactivate across all 21 edge nodes within 60 seconds.
Proactive Prevention: Set up low-balance email alerts or enable automatic recurring top-ups.
BAC-ERR-BILL-302 Medium Severity Billing & Fuel Tank
Raise Ticket

Payment Gateway Handshake Timeout

The payment transaction confirmation from Razorpay or bank gateway timed out or failed signature validation.

Primary Root Causes
  • Bank server communication delay during peak hours
  • User navigated away or closed browser before webhook handshake completed
  • UPI payment authorized but delayed bank settlement notification
Step-by-Step Resolution Guide
  1. Check your bank statement to see if funds were debited.
  2. If debited, allow up to 10 minutes for the automated bank webhook to synchronize.
  3. If not synced after 10 minutes, click "Raise Ticket" with your Payment ID (e.g. pay_XXXXX) for immediate credit application.
Proactive Prevention: Do not close or refresh the payment window until the success confirmation displays.
BAC-ERR-BILL-303 Low Severity Billing & Fuel Tank
Raise Ticket

GST Invoice Generation / PDF Download Exception

The automated billing engine encountered an issue rendering or delivering your official GST tax invoice PDF.

Primary Root Causes
  • Incomplete GSTIN or billing address profile in account settings
  • Transient rendering lock on the invoice document generator
Step-by-Step Resolution Guide
  1. Check Client Settings -> Billing Profile and ensure your Company Name and Address are complete.
  2. Try downloading the invoice again from the Invoices tab after 2 minutes.
  3. Raise a Low priority ticket to request a direct copy sent to your email.
Proactive Prevention: Maintain accurate GSTIN and registered business address in client settings.
BAC-ERR-DOM-401 Medium Severity Domains & Networking
Raise Ticket

Custom Domain CNAME Record Verification Failed

Our global DNS validation cluster cannot detect the required CNAME record pointing to ingress.officialbac.in.

Primary Root Causes
  • DNS changes not yet propagated globally across DNS root servers (takes up to 24-48h, typically 10m)
  • CNAME record configured with typo (e.g. pointing to root domain instead of subdomain)
  • Conflicting A or AAAA records present on the same subdomain
Step-by-Step Resolution Guide
  1. Log in to your DNS provider (GoDaddy, Cloudflare, Namecheap, Google Domains).
  2. Ensure a CNAME record exists for your host (e.g., "app" or "www") pointing to "ingress.officialbac.in".
  3. Remove any conflicting A records for that specific subdomain and click "Verify DNS" in the console.
Proactive Prevention: Use Cloudflare DNS for sub-5-minute DNS propagation worldwide.
BAC-ERR-DOM-402 High Severity Domains & Networking
Raise Ticket

Cloudflare SSL / TLS Handshake Exception

The automated SSL provisioning engine could not issue an Let’s Encrypt / Cloudflare SSL certificate for your domain.

Primary Root Causes
  • Domain DNS points to an outdated IP address or Cloudflare proxy loop (Flexible vs Full Strict)
  • CAA DNS records blocking Let’s Encrypt certificate issuance
  • Too many rapid certificate reissue requests triggered
Step-by-Step Resolution Guide
  1. If using Cloudflare DNS, set SSL/TLS encryption mode to "Full" or "Full (Strict)".
  2. Ensure your DNS CNAME points directly to ingress.officialbac.in with DNS-only (Grey Cloud) during initial verification.
  3. Click "Re-issue SSL Certificate" in your App Detail domain panel.
Proactive Prevention: Ensure your domain provider allows Let’s Encrypt certificate issuance.
BAC-ERR-DOM-403 Low Severity Domains & Networking
Raise Ticket

Official Subdomain Reserved or Already Claimed

The requested *.officialbac.in subdomain is already assigned to another client application or is a protected system keyword.

Primary Root Causes
  • Subdomain slug already registered by another B A C user
  • Subdomain is a reserved administrative keyword (e.g. api, admin, status, docs, mail)
Step-by-Step Resolution Guide
  1. Choose an alternate unique subdomain (e.g. mycompany-app.officialbac.in).
  2. Alternatively, configure a custom domain (e.g. app.yourcompany.com).
  3. Save your Service Configuration and proceed with deployment.
Proactive Prevention: Claim your brand subdomain early during initial service creation.
BAC-ERR-NODE-501 High Severity Edge Infrastructure
Raise Ticket

Regional Edge Node High Latency or Node Unreachable

The selected regional edge node (e.g. IN-WEST-1, IN-SOUTH-2) is experiencing elevated packet latency or undergoing maintenance.

Primary Root Causes
  • ISP transit routing anomaly in the specific geographic region
  • Scheduled edge node software upgrade in progress (<5 min window)
  • Heavy regional volumetric DDoS mitigation active
Step-by-Step Resolution Guide
  1. Check the Live System Status at https://officialbac.in/status for real-time edge node telemetry.
  2. Switch your application Primary Node in Service Configuration to Ahmedabad HQ (IN-WEST-1) or Bengaluru (IN-SOUTH-1).
  3. B A C automated Geo-DNS routing will failover requests to the nearest healthy edge node automatically.
Proactive Prevention: Configure Multi-Zone Geo-Failover in your Service Configuration.
BAC-ERR-SYS-500 Critical Severity System & Gateway
Raise Ticket

Internal Ingress Gateway Fault / Unexpected System Exception

The core platform ingress gateway encountered an unexpected internal exception processing your request.

Primary Root Causes
  • Internal microservice communication fault
  • Database connection pool exhaustion during platform maintenance
Step-by-Step Resolution Guide
  1. Refresh your browser and retry the operation after 30 seconds.
  2. Check the B A C System Status page at /status for platform alerts.
  3. If the issue persists, raise an immediate Critical priority ticket for direct escalation to General Manager Vijay Mudaliyar and engineering leads.
Proactive Prevention: Subscribe to status alerts at /status to receive instant SMS/Email notifications of maintenance.
Was this page helpful?
Need engineering support? Submit a ticket →
Previous B A C Applets & Developer SDK