Recent searches
No recent searches
API error when trying to extract report summary data
Posted May 21, 2024
When trying to extract report summary data, the API throws an error.
Command used:
curl --location 'https://lawnstarter1.tymeapp.com/l5/api/reports/summary' \
--header 'User-Agent: Jersey/2.39' \
--header 'Authorization: Bearer abc' \
--header 'Content-Type: application/json' \
--header 'Cookie: v2-iat=1715598746; v2-token=abc; v2-ttl=259200; wfm-subdomain=lawnstarter1' \
--data '
{
"templateId": "0f617565-e224-4391-af7b-0b8c3e5643ba",
"startDate": "2023-01-01",
"endDate": "2023-05-01",
"selectedGroupingIds": []
}'
And this is the responde:
{
"success": false,
"message": "Invalid response structure fetched from StorageAPI, with message: 'unplanned-time-off' metric: field 'unplannedTimeOffTaskIds' is required"
}
So this report template is the one with issues: 0f617565-e224-4391-af7b-0b8c3e5643ba
Is there a way to fix the problem or to delete the template (given that we don't use it)? We can't delete it ourselves because it's a base template…
0
3 comments
Samanta Velho
Hi Gabriel!
It seems that on the app setup you're missing at leas one time-off reason. When running that report the system will try to find a time-off reason to group the data, but when not finding it, it returns that error. For this to work you should create at least one time-off reason.
Also, I see you are not using our Public WFM API (currently in early access). You can check more detail here in this other community page and this one.
Thanks!
0
Gabriel Rosario
Hello, Samantha, thanks for the response.
I tried to add a time-off reason, but:
1. The Time off reasons card already shows me
“What types of time off agentes can take”
“3 time off reasons”
2. This card is the only one in the “Organization structure” that, when I click in “>”, nothing happens. It should take me to the edit page, right?
Can you help?
0
Samanta Velho
Hi Gabriel!
Not sure why you don't have edit access, it might be something related to permissions? What I can advise now as the fastest course of action is to reach out to support with a screenshot of the steps you listed above, so that they can troubleshot it.
In the meantime I would advise subscribing to the WFM Public API, instead of using that version that is an old access we had to our internal API and it's more prone to change and break any type of integration you're building.
You can find the subscription page here in this community topic, but I'll also leave it here for easier access.
Hope this helps!
0