Skip to main content

I terminated an employee and set their termination date to the previous day, making this change at 12:30 PM. Since then, I’ve been using the updated_since filter to fetch the updated employee list every 15 minutes. However, even though I terminated the employee at 12:30 PM, the API still returns this employee as updated at 1:15 PM. This doesn't seem correct because no further changes were made after 12:30 PM, so there shouldn’t be any new updates for this employee.

Could you clarify why this is happening? if it takes time then how much time will it take to reflect.

Hi Pareek, 

 

I hope you are well. 

 

The frequency at which an API refreshes is determined by the API itself, this is likely something your IT team can advise further on. 

 

It sounds like you updated the employee at 12.30pm but your API didn’t refresh until 1.15pm, which is why it shows as last updated then. I would likely guess your API is refreshing hourly at quarter past but wouldn’t be able to confirm for sure. 

 

I hope this helps! 

 

Zoe :) 

Hi @People Person  , Thank you for reply.  But we’re trying to retrieve updated employees using List Employees API from Personio every 15 minutes using the updated_since filter. However, we encountered an issue where an employee terminated at 12:30 PM still appears in the results for requests with updated_since timestamps after 12:30 PM, even up to 1:30 PM.

Ideally, if I set updated_since to a time after 12:30 PM, this employee should no longer appear, as no further updates were made. Could you clarify the expected behavior for the updated_since filter, particularly around the timing and frequency of refreshes? Also, could you confirm if there’s a delay in data reflection, and if so, how long it typically takes for changes to propagate fully?

 

Hi Everyone,

I posted a question regarding the updated_since filter behavior in the Personio API earlier and would appreciate any help or insights if anyone has faced a similar issue or knows about the expected data propagation time.

If anyone has any experience with this, your input would be really valuable!

Thanks again in advance!

Hi ​@pareek,

Are you considering that this is in UTC? To add more context: updated_since filter uses the UTC time, which means, even though it is currently 4:55 in Germany, for example, the UTC time is currently 3:55 as Germany is in UTC+1. Does this fit in the experience you re having?

I hope this helps! If you have further questions, please let me know! 😃

Wishing you a great rest of the day! 🙌🏼

Best,

Zulema

Hi ​@Zulema T ,

Thank you for the earlier responses. I’d like to follow up as we’re still facing the issue, even after confirming timezone alignment with UTC.

To recap:

  • We terminated an employee at 12:30 PM UTC and set the termination date to the previous day, ensuring the termination took effect immediately.
  • We fetch updates every 15 minutes using the updated_since filter in the List Employees API.
  • Despite this, the employee continues to appear in the API results for requests with updated_since timestamps beyond 12:30 PM UTC, even up to 1:30 PM UTC.

Here’s what we’ve verified:

  1. The timestamps are correctly aligned with UTC.
  2. No further changes were made to the employee record after 12:30 PM UTC.

We’d like further clarification on:

  1. Expected API behavior: Should terminated employees appear in the response beyond the timestamp of their last update?
  2. Known delays: Is there a standard propagation delay for updates to reflect fully in API results?

I want to ensure that my integration behaves as expected and avoids processing outdated data. Your guidance or additional troubleshooting steps would be greatly appreciated.

Your reply


Terms & Conditions of the Personio Voyager Community