This article covers these error messages:
[Destination] is temporarily unavailable. StellarAlgo will automatically retry. (service-unavailable)
[Destination] remained unavailable after multiple retry attempts. Your data was not delivered. (max-retries-reached)
TL; DR
Temporary outages mean the destination is briefly unavailable. StellarAlgo automatically retries, so usually no action is needed on your end. If retries are exhausted and your data wasn’t delivered, check the destination’s status page and try again later.
What This Means
Sometimes a destination platform experiences a brief outage or slowdown. When this happens, StellarAlgo’s push can’t reach the destination. This is almost always temporary and resolves on its own.
There are two messages you might see:
[Destination] is temporarily unavailable. StellarAlgo will automatically retry. We’re still retrying. No action needed.
[Destination] remained unavailable after multiple retry attempts. Your data was not delivered. Retries are exhausted. The push did not go through.
Common Causes
The destination platform is experiencing a service outage or degraded performance.
A temporary network issue between StellarAlgo and the destination.
The destination is undergoing scheduled maintenance.
Rate limiting - too many requests in a short period (StellarAlgo handles this automatically with backoff).
Steps to Resolve
If StellarAlgo is still retrying:
No action needed. StellarAlgo will keep retrying automatically. You’ll see a success notification once the push goes through.
If retries were exhausted:
1. Check the destination’s status page to see if there’s a known outage. Most platforms publish their status at status.[platform].com.
2. Wait for the outage to resolve, then re-run the automation manually.
3. If the destination appears healthy and the error persists, contact StellarAlgo support.
Still Not Working?
If a destination consistently shows as unavailable even when its status page looks healthy, there may be a connectivity or configuration issue. Contact StellarAlgo support with the destination name, automation name, and approximate time of the error.
Related Articles
• Troubleshooting Authentication Errors
• Troubleshooting Configuration Errors