The integration mentioned in this article is currently under development, and the details provided are subject to change. To stay updated on any modifications or enhancements, click the "Follow" button located at the top left corner of this article under the heading.
This article outlines current known issues and limitations with the Humanforce HR to Humanforce WFM integration. It includes resolved items, active investigations, and any required action or workarounds.
We recommend checking this list before raising a support request. This page is kept up to date as changes are released or fixes become available.
Resolved issues
Role revision sync not applying to WFM
Issue:
Role revisions and pay rates for the employee’s primary job were not syncing from HR to WFM. This affected the following fields:
-
Default Award Profile
-
Min/Max Roster Hours
-
Default Pay Rate
-
Default Rate Override
Status:
Resolved – Available via Early Access from 3 March 2025.
Action required:
If you previously had these fields mapped, reset them in Integration Central to ensure sync behaviour applies correctly.
Under investigation
Mapping limits: Award Profile, Pay Rate and Rate Override
Issue:
These fields can currently only be mapped to native Jobs – Remuneration fields in HR. While alternate mappings (e.g. custom fields) are selectable, they won’t pass data to WFM as expected.
Workaround:
None at this stage. Support for custom field mappings is targeted for June 2025.
Role revision date defaults to company start date
Issue:
If the start date of a new employee’s job is different from their company start date, WFM sets the effective role date to the company start date.
Workaround:
Manually update the role effective date in WFM to reflect the actual job start date from HR.
Role revision updates create duplicates instead of replacing
Issue:
If a role revision date is changed in HR after it’s been synced to WFM, a new revision is created in WFM without removing the original entry.
Example:
A role was created in HR with an effective date of 2 Feb 2025, then updated to 22 Feb 2025. WFM stores both revisions instead of replacing the first.
Workaround:
Manually delete the earlier revision in WFM if it no longer applies.
Future-dated roles don’t reflect latest pay rates until import
Issue:
If future-dated role revisions are imported to WFM, the associated pay rates may not reflect the latest values until the next import is run.
Workaround:
Run a daily Employee Import in WFM to keep future-dated role revisions updated with the correct rate.
Emergency contacts and qualifications missing on creation
Issue:
When a new employee is created in HR (via the job.created webhook), emergency contacts and qualifications do not transfer to WFM unless the employee already exists there.
Workaround:
This data will sync correctly on the next job.created or person.updated event, or via the Employee Bulk Import.
Qualification deletions in HR not removed from WFM
Issue:
Deleting a qualification in HR does not remove the equivalent record from WFM.
Workaround:
Manually remove the deleted qualification from WFM to stay aligned with HR records.
All valid qualifications are imported — even if status isn’t “Current” or “Approved”
Issue:
WFM imports any qualifications that are valid on the sync date, regardless of their status in HR. This means “Draft” or other non-approved statuses may appear in WFM.
Workaround:
Only enter qualifications in HR that are ready to sync (e.g. marked as current and complete). We recommend avoiding the use of draft-status qualifications where possible.
Additional information
-
Related guides
- Learn what the integration does – Start with the Overview article to understand the capabilities and benefits of connecting HR to WFM.
- Set up the integration – See the Setup guide for step-by-step instructions on enabling and configuring the integration.
- Understand the data – Refer to the Field mapping reference for full details on what data is synced between systems.
If you're experiencing any other integration issues or need help troubleshooting a sync error, contact Humanforce Support with details and logs (where possible).
This page will be updated as new resolutions or workarounds are introduced.