We open My Arkevia to retrieve a payslip before a bank appointment, and the page remains blank. Or the password is rejected even though we changed it the day before. These blockages often occur at the worst moment, when a document is expected within a few hours. Quickly identifying the cause helps avoid wasting time on unnecessary actions.
Blockage on Safari and iOS: a bug that guides ignore
Most My Arkevia troubleshooting tutorials recommend clearing the cache and restarting the browser. This advice works in many cases, but it overlooks a more specific problem: the reset button may not respond on Safari and iOS.
See also : How to Easily Access Coco.fr Chat: Tips and Steps to Follow
Several users report that the password change procedure gets stuck when using an iPhone or iPad, while it works normally on Chrome or Firefox from a PC. If you find yourself blocked on an Apple device, the most effective reflex is to switch to another browser or a Windows computer.
This is not a network issue or a problem with credentials: it is an incompatibility between the MyArkevia form and Safari’s rendering engine. It becomes clearer why some users describe recurring “bugs,” while the cause lies in the choice of browser. To better understand what to do if My Arkevia is not working, you must first eliminate this hardware variable.
Related reading : Mortgage fees: who pays what and how to anticipate them when buying real estate?
MyArkevia reset email: abnormal reception delays
When initiating a password reset, you expect to receive an email within minutes. On MyArkevia, the delay can reach several hours, and some reports mention a wait of up to nearly 18 hours.
Checking the spam folder is still a good reflex. However, restarting the procedure three times in a row does not speed anything up and may complicate the situation by generating multiple competing links.
What to do while waiting
- Check the spam, junk, and promotions folders in your email, including secondary tabs on Gmail
- Do not immediately restart a second reset request: only one valid link at a time prevents conflicts
- If no email arrives after several hours, contact support at [email protected] specifying your employee ID and the email associated with the account
This latency is not documented in any official guide. Feedback on this point varies over time, suggesting that server load plays a role.
Activation code and employee ID: the necessary step through the employer
One point that many users discover too late: MyArkevia technical support cannot force the activation of an account. If the activation code was never received, if the employee ID is incorrect, or if the temporary secret code is rejected, only the HR service of the company can intervene.
Cegedim, the publisher behind Arkevia, manages the technical infrastructure. Personal data (employee ID, activation email, connection to the digital vault) are the responsibility of the employer. This division of responsibilities creates a frustrating gray area.
Situations that require direct HR contact
- Account never activated despite several months of seniority in the company
- Employee ID untraceable or not corresponding to any personal space
- Temporary secret code expired or rejected without an explicit error message
- Email address change not reflected in the system
In these cases, writing to Arkevia support only prolongs the process. Contacting your HR department directly remains the shortest path to unlock access to online payslips.
Server outage or MyArkevia maintenance: distinguishing the two
When the site is completely inaccessible, one tends to think the problem is on their end. Before clearing the cache or reinstalling anything, it is essential to check if MyArkevia is under maintenance or experiencing an outage.
Maintenance is not always announced. A site like DownDetector allows you to cross-reference reports from other users in real-time. If reports increase at the same time, you know the problem is on the server side and that no local action will change anything.
Reflexes in case of confirmed unavailability
Waiting one to two hours before trying to reconnect is sufficient in most cases. If the blockage persists beyond half a day, an email to [email protected] with a precise description of the problem (error message, browser used, time of attempt) allows for reporting the incident.
The employer is still required to provide payslips upon request, even in the event of a prolonged platform outage. A payslip can be transmitted through another channel if the situation demands it. This point is often overlooked, but it protects the employee regardless of the reliability of the digital vault.
When you combine an incompatible browser, a delayed reset email, and an unresponsive HR service, frustration can quickly mount. Identifying the right contact based on the nature of the blockage (technical or administrative) saves considerable time, especially when a document is urgently needed by a third party.