# Migrating Sandbox -\> Cloud Join Issues

**URL:** <https://www.thethingsnetwork.org/forum/t/migrating-sandbox-cloud-join-issues/74047>\
**Category:** Uncategorized\
**Created:** [August 6, 2026, 10:01pm UTC](https://www.thethingsnetwork.org/forum/t/migrating-sandbox-cloud-join-issues/74047 "2026-08-06T22:01:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![martinfbrandt](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/m/e5b9ba/32.png) [@martinfbrandt](https://www.thethingsnetwork.org/forum/u/martinfbrandt)\
**Post date:** [August 6, 2026, 10:01pm UTC](https://www.thethingsnetwork.org/forum/t/migrating-sandbox-cloud-join-issues/74047/1 "2026-08-06T22:01:56Z")

</div>

Hello,

I’m migrating our fleet from the Sandbox version of TTN into the Cloud Discovery version and following this guide: [Between The Things Stack distributions | The Things Stack for LoRaWAN](https://www.thethingsindustries.com/docs/concepts/migration/migrating-between-tts-distributions/) .  
I’ve moved three of my devices over (waiting to move Gateways at a later date), and i’m getting join requests successfully to my devices on the Cloud version (screenshot attached). However, the devices don’t ever seem to receive any data. The uplinks are still happening on their regular cadence, but they’re just the join attempts.

Any thoughts on what’s going on here?

 ![Screenshot 2026-08-06 at 3.59.02 PM](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/7/3/7389e835dd62c4c13bec2ef1b08fc89a6c613fe1.png)

---

<div class="post-metadata">

**Author:** ![siva96](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/s/49beb7/32.png) [@siva96](https://www.thethingsnetwork.org/forum/u/siva96)\
**Post date:** [August 20, 2026, 1:36pm UTC](https://www.thethingsnetwork.org/forum/t/migrating-sandbox-cloud-join-issues/74047/2 "2026-08-20T13:36:22Z")

</div>

Hi Martin,

My guess is that downlink scheduling has been disabled for this device. If so, the Network Server never transmits the join-accept, which would explain why every uplink is another join attempt.

Could you check it with the CLI?

**Step 1:** Configure the [Things Stack CLI](https://www.thethingsindustries.com/docs/the-things-stack/interact/cli/) to talk to your Cloud tenant — see [Configuring the CLI](https://www.thethingsindustries.com/docs/the-things-stack/interact/cli/configuring-cli/).

**Step 2:** [Log in with the CLI](https://www.thethingsindustries.com/docs/the-things-stack/interact/cli/login/) to your tenant.

**Step 3:** Read the current value:

```auto
ttn-lw-cli dev get --application-id <application-id> --device-id <device-id> --mac-settings.schedule-downlinks

```

**Step 4:** If it comes back `false`, enable it:

```auto
ttn-lw-cli dev set --application-id <application-id> --device-id <device-id> --mac-settings.schedule-downlinks=true

```