When it happens
These messages appear when a request fails because the MyFitnessClient server is temporarily down, did not respond in time or received too many requests. You see the message in a temporary notice after an action, such as saving, sending or deleting, or in an error message inside a window. Professionals and clients see them, on the website and in the app.
Each message says what failed:
| Message | What happened | Where it appears |
|---|---|---|
| “The server is temporarily unavailable.” | The MyFitnessClient server was not available to respond. | Website and app |
| “The server took too long to respond.” | The MyFitnessClient server did not respond in time. | Website and app |
| “Too many requests in a row. Wait a moment and try again.” | Many requests arrived in a short time and this one was stopped before it reached the server. | Website and app |
| “The service is temporarily unavailable.” | The server received the request, but a temporary database failure prevented it from completing it. | Website and app |
| “Server temporarily unavailable. Try again in a moment.” | The website could not connect to the MyFitnessClient server. | Website |
| “Couldn't reach the server. Try again.” | The server answered the website in a way the website could not read. | Website |
| “The request took too long.” | The website stopped waiting for the response: after 30 seconds when loading data, 45 seconds when saving, sending or deleting, and 5 minutes when finishing a file upload. | Website |
| “Too many requests. Wait a moment.” | The MyFitnessClient server itself received many requests in a short time and refused this one. | Website |
| “Too many attempts.” | The same case as the previous row. | App |
When a page or a list on the website does not load, the error card shows its own title, such as “Service temporarily unavailable” or “Too many requests”, and not these messages: see “We could not load this information” and other error cards. If the message mentions the security protection, see “The request was blocked by the security protection”: what to do.
Steps
To repeat the action:
- Wait a few seconds without repeating the action.
- If you were saving, sending or deleting, check on the screen or in the list whether the action went through: most of these messages do not say whether the server completed it.
- Repeat the action once.
- If the same message comes back, wait a few minutes and try again.
- If it keeps happening, contact support as described in “If this did not solve it”.
When the server responds, the action goes through and the notice does not come back.
Data sent is too large
The message “The file or data you sent is too large.” appears when the request is refused because of its size before it reaches the MyFitnessClient server. That is why it does not say what the limit is. Reduce what you are sending, for example a shorter video, less text or the content split into parts, and try again.
The message “File is too large.” is a different one: it comes from the MyFitnessClient server itself, which has limits for each file and for each request. On the website, when what you save is text and not a file, for example a very long description or page, the same refusal shows “This content is too large to save.”
In the app
The messages in the table that appear in the app show up in the notices after an action and also on the card of a page that did not load, except “Too many attempts.”: that card keeps the screen's own message. Some screens show their own message. There are four differences from the website:
- When a page does not load because of one of these errors and the phone has a saved copy of that page, the app shows the copy instead of the message.
- With a server error, the app usually requests the page again on its own up to two times before showing the message.
- An entry that the app saves on the phone first, such as a checked habit, does not show these messages when sending fails because of one of these errors: it stays queued and the app sends it again on its own.
- In general, these errors do not make the “Offline” banner appear, because the server responded. If the app says “No connection. Check your internet and try again.” and you have internet, the request did not reach the server or got no response within 15 seconds: see The app says “Offline” or takes a long time to load.
Common problems
The same message comes back every time I try again
The server is still unavailable or busy. Wait a few minutes before trying again, instead of repeating right away. If the message is still there after several minutes, contact support.
“Too many requests in a row” appeared after selecting the same button several times
Each time you select the button, a new request goes out. Wait a moment without selecting anything and repeat the action once.
Questions
Is the problem with my account?
No. These messages are about the MyFitnessClient server and do not depend on your account, your plan or team permissions. A permission problem shows a different message, for example “You don't have permission for this action.”
Did the action go through?
With “Too many requests in a row” and with “The file or data you sent is too large.”, no: the request was stopped before it reached the server. With the other messages, it may have gone through: check on the screen or in the list before repeating it.
If this did not solve it
Write to the MyFitnessClient team through the contact on the “Didn't find what you're looking for?” card, at the end of the Help Center home page. In the app, the same card, at the end of the Help Centre, shows the email for problems with the app. If you are a professional, you can also create a request in Support, in Settings. Send:
- the exact message that appeared;
- the day and time it appeared;
- what you were doing and on which page;
- whether the message comes back every time you repeat the action;
- whether you use the website, and with which browser, or the app, and on which phone.