**This 302 redirect in a WordPress Multisite setup is likely caused by how WordPress handles requests when it's running as a multisite network and trying to resolve sites that aren’t fully configured.

Here’s what could be happening:

---

1. **Default WordPress Behavior:**
WordPress often uses `wp_redirect()` for multisite sub-site resolution. If a site isn’t fully set up or mapped properly, WordPress may default to a temporary 302 redirect.

2. **ELB-HealthChecker/2.0 (from AWS):**
This request is from **AWS Elastic Load Balancer (ELB)** health checks. ELB makes a plain `GET /` request. If the root site (or sub-site) is not fully responding or mapped, WordPress may redirect it with a 302 temporarily.

3. **Multisite Rewrite Rules:**
Your `.htaccess` rewrite rules seem mostly correct, but the custom rules at the end (`wptmj/$2`) may be misrouting requests, especially if `wptmj` is not a valid subdirectory or symlinked path.

---

### ✅ What You Can Try:

#### 1. **Force WordPress to Use 301 Redirects:**
You can try modifying redirection functions using `wp_redirect_status` hook in `functions.php`:

```php
add_filter('wp_redirect_status', function($status) {
return 301; // Force 301 instead of 302
});**