GoDaddy applies a default TTL of one hour to records you create in its DNS management panel, so once you edit an A, CNAME, MX, or TXT record, resolvers that already cached the old value will keep serving it for up to an hour before picking up the change. In practice many locations update sooner, because not every resolver had the record cached at the exact moment you saved. If you know a change is coming, lower the TTL to 600 seconds a day ahead of time so the switch rolls out in minutes instead.
The slow case at GoDaddy is switching nameservers — for example moving DNS hosting to Cloudflare or Route 53, or moving back to GoDaddy's own nameservers. That change lives in the .com (or other TLD) delegation and is cached far longer than an ordinary record, so it genuinely can take up to 24 to 48 hours to settle everywhere. GoDaddy's own dashboard often warns about this window, and the warning is honest: nameserver delegation is the one place where the old 'up to two days' rule still applies.
A common source of confusion is GoDaddy's own caching and the difference between 'saved' and 'propagated'. The panel confirms your edit instantly, but that only means GoDaddy's authoritative servers have the new value; the rest of the internet catches up on its own schedule. Rather than refreshing your browser and clearing your cache repeatedly, query the record from many locations at once to see the real state of propagation.