The position follow-up process failed because of an error in a prior global assignment process.

[zekeryaunal]

Hi,

When we create a Global Assignment for a user in the system, the “Away on Global Assignment” and “Back from Global Assignment” records are not automatically created in the Job Information of the Home Assignment.

Although the Right to Return configuration is active, the related records do not appear in the Home Assignment profile.

When we check the issue in Admin Alerts, we see the following error message: “The position follow-up process failed because of an error in a prior global assignment process. Check your global assignment configuration. Then, retrigger the admin alert.”

What could be the reason for this error?
We would appreciate your support on this topic.

[T_Eva]

Hi @zekeryaunal ,

Please check below information for troubleshooting and analysis of your issue.
In case none of below information can help with your issue, then please document your process end-to-end and share with Product Support Team.

Step-by-step troubleshooting checklist

Follow this sequence to pinpoint the cause quickly.

A. Verify process and template

• Ensure you used the Global Assignment wizard (not Concurrent Employment).
• Confirm the correct GA template is assigned and active.

B. Validate Event + Event Reason setup

• Admin Center → Manage Organization, Pay and Job Structures → Event Reason:
  • Verify two dedicated Event Reasons exist and are Active:
    • For GA start (used by the wizard to write “Away on GA” on Home)
    • For GA return (used to write “Back from GA” on Home)
  • Check Employee Status on these Event Reasons (commonly remains “Active” for Home assignment while status is “Away on GA” at the assignment level).
  • Ensure RBP permissions include these Event Reasons for the acting user.

C. Validate Position Management “Right to Return”

• Admin Center → Position Management Settings → Right to Return:
  • Ensure Right to Return is enabled.
  • Map the Event Reasons for Away/Back exactly to those from step B.
  • Confirm behavior for Home position during GA (reserve, allow other occupant, etc.) is consistent with your position capacity and multiple-incumbent settings.
• Admin Center → Position Management Settings → General/Sync/Rules:
  • Review any Position Sync rules executed during GA start/end. Temporarily disable custom rules to test.

D. Check business rules and required fields

• Admin Center → Configure Business Rules:
  • Identify onSave/onChange rules for Job Information and Position that trigger on GA events.
  • Look for mandatory-set logic that could reject the Home “Away/Back” record or the position follow-up (for example, requires cost center or custom field that’s not set on Home at that time).
  • Temporarily deactivate non-critical rules and re-test to isolate the culprit.

E. Check permissions

• RBP → Role(s) of the acting user:
  • Job Information: Edit permission for the Home employment
  • Position object: View/Edit permission and field-level permission necessary for follow-up
  • Event Reasons used by GA (start/return)
• If Centralized Services for Job Info is enabled, ensure the user has the right permissions to pass CS validations.

F. Use Admin Alerts and Execution Manager to get detail

• Admin Center → Admin Alerts:
  • Open the Position Follow-Up alert and view details; it often references which record/action failed.
  • After correcting config, use “Retrigger” as the alert suggests.
• Admin Center → Execution Manager:
  • Check any Global Assignment, Position Sync, or Centralized Services logs for stack messages pointing to missing mapping/permissions.

---

Quick remediation playbook

• Most frequent fix:
  • Correctly map the Event Reasons for GA start/return in Position Management → Right to Return.
  • Ensure those Event Reasons exist, are active, and have appropriate Employee Status settings.
  • Grant RBP to edit Job Info on the Home employment and to update Position during follow-up.
  • Retrigger the Admin Alert.
• If still failing:
  • Temporarily disable custom Job Info/Position rules and retry; if success, reintroduce rules and fix the one that blocks the automated record creation.
  • Check multiple-incumbent and position capacity settings; align with your chosen Right-to-Return behavior.

---

Preventive best practices

• Keep dedicated Event Reasons for GA Away/Back, and do not reuse them for unrelated processes.
• Test GA with a minimal ruleset first; then layer custom rules to catch conflicts early.
• Align Position Management multiple-incumbent/capacity rules with your Right-to-Return setting to avoid occupancy conflicts.
• Document and permission the “automated” actor path for GA follow-up (who runs the action and what they can modify).

Hope this information can help you.

Regards.

Thiago Eva