This guide helps resolve cases where data updated in Cornerstone (e.g., employee details or leave requests) doesn’t sync to edays. You’ll learn how to work with Cornerstone’s support team to quickly identify the root cause.
How Data Synchronisation Works
Cornerstone controls data flow: Changes only sync to edays when Cornerstone actively sends updates via its API calls.
edays is "listening" only: Our API does not fetch data automatically from Cornerstone. If Cornerstone needs edays data, it must call our API using
GETmethods.Key point: If data exists in Cornerstone but not in edays, the issue likely starts with Cornerstone’s API call not reaching us successfully.
How to Troubleshoot Missing Data
Follow these steps:
Identify one clear example
Note a specific employee/user affected (e.g., "John Doe’s leave request on [date]").
Record the exact data missing (e.g., leave balance, hire date).
Contact Cornerstone support
Raise a ticket with Cornerstone’s support team (not edays). Include:
A description of the missing data and affected employee.
This request:
*"Please provide for one affected user/API call:
Endpoint and method used to sync data to edays (e.g.,
POST /leave-requests).JSON payload sent (for
POST/PUT/PATCHcalls).Timestamp of the API call attempt (include time zone)."*
Share details with edays
Once Cornerstone responds, forward their findings to edays support. We’ll check:
Whether the call reached our system.
If the request was processed correctly.
Additional Information
Key terms:
Endpoint: The edays "address" Cornerstone calls (e.g.,
https://api.edays.com/leave-requests).Method:
GET(fetch data),POST/PUT/PATCH(send/modify data).JSON payload: Data sent to edays (like an instruction note).
Timestamp: Exact time the sync was attempted (e.g.,
10 June 2025, 14:30 GMT).