![Untitled design (1)-Aug-01-2022-12-37-27-80-PM.png]](https://help.syscloud.com/hs-fs/hubfs/Untitled%20design%20(1)-Aug-01-2022-12-37-27-80-PM.png?height=40&name=Untitled%20design%20(1)-Aug-01-2022-12-37-27-80-PM.png){kind=small}
Slack Backup: Temporary Limitations
This article explains the temporary backup limitations you may see for Slack in SysCloud. It covers Slack channels, messages, files and users. Temporary limitations clear on their own, and in most cases you don't need to do anything.
What is a temporary limitation?
A temporary limitation means some data was not backed up in one backup attempt because of a short-lived condition, such as a Slack request limit, a brief service outage or a network interruption.
- The backup status shows Retry in progress for the affected data.
- SysCloud retries the affected data automatically, usually in the next backup cycle.
- The rest of your backup continues as normal, and nothing already backed up is affected.
How to use this article
- In SysCloud, open the backup details and note the message shown for the affected channel, item or user, and its backup status.
- Find that message in the quick reference table below.
- Read the matching section for what it means and what to do.
Quick reference
| Limitation | Message shown in SysCloud | Backup status | Action |
|---|---|---|---|
| 1. API request limit reached | API request limit reached | Retry in progress | No action needed |
| 2. Slack temporarily unavailable | Service temporarily unavailable | Retry in progress | No action needed |
| 3. Temporary connection issue | Temporary connection issue | Retry in progress | No action needed |
| 4. Temporary operation conflict | Temporary operation conflict | Retry in progress | No action needed |
Limitations in detail
1. API request limit reached
Message shown in SysCloud:
- API request limit reached
Backup status: Retry in progress
What happened
Slack limits how many requests an app can make in a given period. The backup reached that limit, so some data was not backed up in this attempt.
What you can do
No action is needed. SysCloud retries the affected data automatically in the next backup cycle.
2. Slack temporarily unavailable
Message shown in SysCloud:
- Service temporarily unavailable
Backup status: Retry in progress
What happened
Slack was temporarily unavailable during the backup attempt, for example because of a short outage or maintenance, so some data was not backed up.
What you can do
No action is needed. SysCloud retries the affected data automatically in the next backup cycle.
3. Temporary connection issue
Message shown in SysCloud:
- Temporary connection issue
Backup status: Retry in progress
What happened
A temporary network connection issue interrupted SysCloud's access to Slack during the backup attempt.
What you can do
No action is needed. SysCloud retries the affected data automatically in the next backup cycle.
4. Temporary operation conflict
Message shown in SysCloud:
- Temporary operation conflict
Backup status: Retry in progress
What happened
Slack reported a temporary conflict while SysCloud was processing the affected data, for example because the data was being changed at the same time. The data was not backed up in this attempt.
What you can do
No action is needed. SysCloud retries the affected data automatically in the next backup cycle.
Frequently asked questions
Do I need to start a backup manually?
No. SysCloud retries the affected data automatically.
Was any data lost?
No. The data is still in Slack. It wasn't copied in that attempt and is backed up when SysCloud retries. Nothing already backed up is affected.
When should I contact support?
If the same message keeps appearing for the same channel, item or user over several backups in a row, contact SysCloud Support.
Why does this happen more after I first connect an account?
The first backup reads all of your data, which makes many more requests to Slack than later backups. Request limits are reached more often during that first backup.
Need more help?
Contact SysCloud Support and include:
- A screenshot of the message shown in SysCloud, or the exact message text
- The affected channel, item or user
- The date and time of the backup
Related article: Slack Backup: Permanent Limitations