Recent searches
No recent searches

Samanta Velho
Joined Dec 14, 2023
·
Last activity Feb 20, 2025
Following
0
Followers
0
Total activity
81
Votes
0
Subscriptions
32
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Samanta Velho
Samanta Velho commented,
Hi Chris,
Thank you for all the feedback you provided! I’m glad to hear that it aligns with the insights we’ve been receiving from other early access participants. Here’s a bit more detail on your points:
- Relationships in the Reports Endpoint: We’ve received similar feedback regarding the relationships in the Reports endpoint. One of the planned improvements is to create a user management endpoint that will contain the user data currently available only in the relationships section. Additionally, we’re looking to develop endpoints for workstreams and general task information, which will help ensure everything can be properly mapped. We’re still discussing when we can start working on these improvements, so we don’t have an ETA just yet.
- Data Pulls and Real-Time Data: We’ve noted that many participants in the early access program would like the ability to collect more than one day of data. The ability to pull real-time data is also on our roadmap. We’re working to understand the most pressing needs and prioritize improvements accordingly.
-
Time-Off Requests: This is related to both the WFM Public API and our integrations work. We’re currently developing a time-off endpoint in the WFM Public API and working on an integration with an HRIS system (though it’s not Paycom). Once we have that integration up and running, we’ll be looking into other possible integrations, and the process should be quicker due to the learnings from our first integration.
CC: Maksym Shynkarenko Rita Goncalves Tiago Magalhaes Joanna Zoła Copying my colleagues that work with other areas of our Product so that they are also aware of your feedback.
Thanks again for your valuable input! If you have any more thoughts or questions, feel free to share.
Best,
Samanta
View comment · Posted Feb 04, 2025 · Samanta Velho
0
Followers
0
Votes
0
Comments
Samanta Velho commented,
After reviewing the most recent logic on how we deal with timezones and API calls, this is how it behaves today:
1. Reports Endpoint:
- The startTime timestamp now respects the timezone of the report.
- For example, if your report is configured in Sydney timezone and you provide a Unix timestamp for 00:00 Sydney time on the 6th, the response will reflect data in Sydney timezone.
- Additionally, if you provide a timestamp within the day (e.g., 05:00), the system adjusts to include the full day, from 00:00 to 23:59 in the report’s timezone. This ensures the report always covers an entire day of data, aligned to the report's timezone settings.
This means you won't need to make 2 separate calls to cover the 24h for EST - I will also update the community topic to reflect this update
2. Agent Activity Endpoint:
- The startTime parameter behaves differently. It includes activities starting from the given timestamp as well as activities that began earlier but were still ongoing at the specified time.
- For example, if you request data from 10:00, the response will include all activities that started at or before 10:00 and ended after 10:00.
View comment · Posted Jan 08, 2025 · Samanta Velho
0
Followers
0
Votes
0
Comments
Samanta Velho commented,
Hi Fares,
Taking into consideration that your startTime UTC is 1736139600
(which is equal to January 6, 2025, 00:00:00 EST), 1736139600
needs to be your start and end time, but in the API response if you have a timestamp equal or higher to 1736225999 then you know that, that will be already the 7th!
Hope this helps!
Samanta
View comment · Posted Jan 08, 2025 · Samanta Velho
0
Followers
0
Votes
0
Comments
Samanta Velho commented,
Hello Fares,
While the API returns data for a full UTC day, you can still retrieve data for a single EST day by using specific UTC timestamps. Here's how you can do it:
Example for January 6th, 2025 (EST), the start and end UTC timestamps would be:
-
Start:
1736139600
(equivalent to January 6, 2025, 00:00:00 EST) -
End:
1736225999
(equivalent to January 6, 2025, 23:59:59 EST)
By including these timestamps in your request, you'll effectively retrieve data for a single day in EST.
Let me know if you have any further questions or need assistance!
Best regards,
Samanta
View comment · Posted Jan 06, 2025 · Samanta Velho
0
Followers
0
Votes
0
Comments
Samanta Velho commented,
I’ll pass along the URLs you just sent to the team, and I’ll get back to you as soon as we have any updates or if we need more information to troubleshoot the issue further.
Best regards,
SV
View comment · Posted Jan 06, 2025 · Samanta Velho
0
Followers
0
Votes
0
Comments
Samanta Velho commented,
I’m bringing this again to my colleagues' attention so they can review the situation. In the meantime, to expedite the troubleshooting process, could you please share the URL you’re using to make the request that is returning the 500 error?
Thank you!
Best,
SV
View comment · Posted Jan 06, 2025 · Samanta Velho
0
Followers
0
Votes
0
Comments
Samanta Velho commented,
Request #13227646 "Request created from: API 500 Se..." was closed and merged into this request. Last comment in request #13227646:
This request was created from a contribution made by Bruno Alcantara on January 06, 2025 10:34 UTC.
--
Hi 6023917640858 ,
We continue to face the same issue and it has been failing almost everyday.
This is a daily report, so we have to manually process it again one by one.
Could you please, assist on how could we improve this?
View comment · Posted Jan 06, 2025 · Samanta Velho
0
Followers
0
Votes
0
Comments
Samanta Velho commented,
Request #13212337 "Request created from: API 500 Se..." was closed and merged into this request. Last comment in request #13212337:
This request was created from a contribution made by Bruno Alcantara on December 19, 2024 08:58 UTC.
Link: https://support.zendesk.com/hc/en-us/community/posts/8570404371866-API-500-Server-Error
--
We have been seeing a lot if instability for extracting the report information through API. While not ideal, usually retrying it makes it work, but no luck today…
We haven't changed anything today, could you help please?
We need support.
500 Server Error: Internal Server Error for url: www…
View comment · Posted Dec 27, 2024 · Samanta Velho
0
Followers
0
Votes
0
Comments
Samanta Velho commented,
Thank you for reaching out regarding the instability you’ve been experiencing with the API for extracting report information. I apologize for the inconvenience this has caused. I was out of the office for a few days, but I’m back now and ready to help you.
To better understand the situation, could you please provide some feedback on whether the issue has persisted since you reported it on the 19th? Specifically, I’d like to know if you’re still encountering problems as of today, the 27th, or if the issue has resolved but occurred over a period of time.
Your input will be very helpful in investigating this matter.
Thank you for your patience, and I look forward to your response.
Samanta
View comment · Posted Dec 27, 2024 · Samanta Velho
0
Followers
0
Votes
0
Comments
Samanta Velho commented,
Hi Fares,
Thank you for reaching out via the community forum! Your question is valuable and can help other WFM API users who may have similar concerns.
To clarify, our database operates in UTC, which is the reference time for all timestamps. When you enter a Unix timestamp, it is interpreted in UTC. Using your example (startTime: 1734488584) it would mean that:
- UTC: December 18, 2024, 00:03:04 to December 19, 2024, 00:03:04 (24h)
- GMT: December 18, 2024, 00:03:04 to December 19, 2024, 00:03:04 (24h)
- EST: December 17, 2024, 07:03:04 PM to December 18, 2024, 07:03:04 (24h)
I hope this helps clarify your concerns regarding timezones! If you have any further questions, feel free to ask.
Samanta
View comment · Posted Dec 27, 2024 · Samanta Velho
0
Followers
0
Votes
0
Comments