RM API Latency / Inconsistent Results

Has anyone else noticed poor performance and/or data inconsistency with the Resource Management API in the last 48 hours? I see the documentation site was updated yesterday - did anything change with the API itself?

We have a weekly timesheet integration process that relies on the Resource Management time entries endpoint to extract last 30 days of time entries along with their approvals data. It has been in place in production going back to 2021. Yesterday, I started seeing intermittent problems where the API response will take forever to return or timeout altogether. Also, when paging through the data, I am seeing some records duplicated and others not returned at all. The behavior has continued today and afraid it is going to impact our weekly time processing that happens later today

Find more posts tagged with

Accepted answers

All comments

Isaac A.

Hi there,

I checked the Resource Management API Changelog to see what might have changed.

You are correct that the documentation was updated recently. I can see a fix from 2025-10-27:

2025-10-27 Describe how to change assignment to different project or phaseFIX:We fixed the documentation to reflect that changing an assignment to a different project or phase requires deleting the current assignment and creating a new one.We updated the documentation on the following operation pages:
PUT /assignments/{assignment_id} (Update assignment)
PUT /users/{user_id}/assignments/{assignment_id} (Update user assignment)

This change was a documentation fix to clarify how to update assignments and removed the assignable_id from the PUT /assignments/... endpoints.

This change is related to the assignments endpoint and should not impact the performance or data structure of the time entries endpoint you are using. The documentation was updated, but this change would not explain the latency or data inconsistency you're seeing.

I have not seen other reports of this specific issue on the time entries endpoint.

In case you have identified an issue that is affecting you, please don't hesitate to contact the Support Team directly.

I hope this helps!

Cheers,
Isaac.

Sign in to join the conversation!

Quick Links

Component react.discussion.discussions had an error.

ref must be one of: categoryID, siteSectionID, category, category/categoryID, category/name, category/description, category/url, category/allowedDiscussionTypes, locale, siteSection, siteSection/basePath, siteSection/contentLocale, siteSection/sectionGroup, siteSection/sectionID, siteSection/name, siteSection/description, siteSection/apps, siteSection/attributes, layoutViewType, discussionID, commentID, page, latest, sort, sortType, lookupSort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.