Does Personio Remember Between Runs? The Employee Profile Holds. The Run Reasoning Does Not.
Does Personio Remember Between Runs? The Employee Profile Holds. The Run Reasoning Does Not. Short answer: Personio keeps a deep record for every employee, and that record holds a great deal. An employee profile can store more than 200 attributes, from address and team to cost center, bank details, and emergency contact. Profile history shows when a value changed. Workflows for onboarding, offboarding, and approvals keep their steps and activity. What does not hold in the same way is the work a
Does Personio Remember Between Runs? The Employee Profile Holds. The Run Reasoning Does Not.
Short answer: Personio keeps a deep record for every employee, and that record holds a great deal. An employee profile can store more than 200 attributes, from address and team to cost center, bank details, and emergency contact. Profile history shows when a value changed. Workflows for onboarding, offboarding, and approvals keep their steps and activity. What does not hold in the same way is the work a scheduled run does across many employees, teams, and locations at once. The comparison, the order, and the reasons behind both are not saved as a history the next run can load.
What one profile keeps in Personio
Personio was built as a core system for people data, so its memory is organized around the employee. The center is the employee profile.
That profile is the single source of truth for a person at work. Standard fields cover personal details, employment details, team, role, and location. Custom attributes extend it further, for languages spoken, job family, level, or the date of a last salary change. Because the profile is structured, a later process does not guess. It reads the same fields every time.
History adds a second layer. Personio lets a team look back at an employee record and see when changes were made to the profile. A move, a team change, or a salary update leaves a trace in that history, so a question about what changed can be answered from the record itself.
Scheduled changes add a third layer. A change that is known in advance, such as a future address change or a salary increase that starts next month, can be entered early with an effective date. Several consecutive changes for the same attribute can sit in order, each waiting for its date. The system remembers a future fact before it becomes a current fact.
That is durable, profile-level memory. It answers who this person is, where that person sits in the company, and what is scheduled to change.
What workflows, reminders, and activity keep moving
Around the profile, Personio keeps work moving in several ways.
The Automations area holds workflows for repetitive tasks, including onboarding and offboarding, approvals, signature requests, and custom workflows built for an organization. A workflow defines the steps that should happen when a trigger fires, such as a start date arriving or a status changing. The definition persists, so the same path runs the same way each time.
Reminders sit beside workflows. A reminder can be created for an employee role, so a task tied to a date or an event does not depend on a person remembering to chase it. Approvals have their own flow, with requests, decisions, and an activity view that shows what is open and what has finished.
Activity is the record of execution. The Activity tab shows running workflows and past executions, plus approval activity. A team can monitor progress, spot a bottleneck in an onboarding path, and check the status of each task.
Each layer works well on its own terms. The profile preserves the person. The workflow preserves the process. The activity view preserves the execution log. Notice what every layer reads from: the stored record as it stands today. None of those layers was built to hold conclusions that belong to a run across all of them.
Where a scheduled run starts from zero
Picture a recurring automation that works a Personio pipeline on a schedule. Each run pulls employees across several teams, compares who is due for a review, a contract change, or an onboarding step, checks who was already handled for a similar reason, and decides who should move first and why.
The profile helps with the first step only. It gives the run today's attributes, today's team, and today's scheduled changes. The workflow helps with the second step only. It gives the run today's steps and today's approval state.
What the run worked out last time lives in none of those places. Which employees were set aside because a manager changed the criteria mid-cycle. Which near-miss from a closed review round was marked as the first check for the next round, and the exact reason. Which comparison across two locations settled a tie, and what evidence settled it. That reasoning was produced by the run, across records, and Personio's employee-centered store has no field for it.
So the next run re-derives it. It re-reads the same profiles, re-applies the same filters, and re-makes the same comparisons, often reaching a slightly different order because the starting context was never saved as a shared history. The records remember the people. The run itself is forgotten.
Give the run a memory of its own
The fix is a memory layer that sits outside any one employee record and holds the run's own work. Vilix AI is built for that job.
Vilix AI is cloud-hosted, so there is zero infrastructure to set up or manage. An automation connects once over MCP, and the same memory is then available everywhere that connection runs, on every tool and every schedule, not locked inside one platform's database. When a run finishes a comparison, a ranking, or a decision about a group, it saves that work to Vilix AI. When the next run starts, it loads that history first, before it touches a single profile.
That history is full conversation history, not just facts. A saved fact can say an employee was flagged for review. Full history keeps the exchange that led there: the criteria used, the employees compared, the reason one was placed ahead of another, and the note that changes the order next time. A later run, or a different agent working the same people process, reads the reasoning, not only the result.
Start with the free plan, which is free forever. A 7-day Pro trial is available with no credit card required for teams that need more. Data stays portable the whole time: export everything or delete it anytime.
Personio will keep doing what it does well. The employee profile will hold, the workflow will hold, and the activity log will hold. Add a memory that holds the run as well, and a scheduled people process stops starting from zero. It starts from last time, with the reasons included.