Recent searches


No recent searches

API 500 Server Error



Posted Dec 19, 2024

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…


0

19

19 comments

Hi Bruno,
 
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

0


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…

0


Hi Samanta Velho ,

 

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?

0


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.

Link: https://support.zendesk.com/hc/en-us/community/posts/8570404371866-API-500-Server-Error#community_comment_8659148502554

--

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?

0


Hi Bruno,
 
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

0


Thanks for sharing, Bruno!
 
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

0


Hello,
 
The following has been tested
https://rebuy.zendesk.com/wfm/public/api/v1/reports/cacffeb4-ccf8-464c-b98a-7b1258ff1d48/data?startTime=1734480000&endTime=1734480000&page=1
and got 200 back.
Account is assumed with Daniel Freudenberger - df@rebuy.com and API request is trigger under that account. Image is attached.
 
Best regards
 

0


Hey Samantha,

The problem is intermittent.

I attached some pictures for reference, from this morning.

 

Could you also share a timeline for the early program to conclude? :)

0


Hi Bruno,
 
Thank you for the additional information you have provided. 
 
I'm Joanna, product manager for the team that is addressing problems with the WFM Public API EAP. Me and Marko Pavlovic (our Engineering Manager) will continue to assist you with addressing errors you are experiencing. 
 
I have brought this additional information to the attention of the team.
 
At this point the plan is for the WFM Public API to continue as an early access program.
 
Best regards,
Joanna Zola

0


Thank you Joana, for the information.
Hopefully we get this working smoothly soon, would you please have an update?

The issue persists.

Thank you!

0


Hi Bruno.
 
Jumping in here. 
Can you share time when you are triggering this script?
We can see 4:04
It is reports API with pagination for the previous day as we can see
Thank you in advance.
 
Respect,
 
Marko

0


Hi, Marco!

Yes, the time we are triggering for these 2 are 4:04 and 05:11
We need to fetch different reports from tymeshift.

0


Marko*,  sorry

0


Thank you Bruno.
No worries at all.
Let us look into our logs what is happening.
Meanwhile we will trigger calls on our end.
In browser we see 200.
Might be we would need to load the calls via Postman. If that is the case could we organize a session to share temp API token?

0


We can organize to share the token, how can I share it without being public?

Could you create a ticket per mail, requesting the token, please?

 

Question: don’t you capture WFM API endpoints in support Admin?

If so, the failures would be easily identifiable.

0


Good day Bruno,
Any updates on our end regarding API requests?
Do you see change in stability and moving away from Error 500 in past days?
 
On a note of sharing the token, we have a workaround. 
If still needed  following steps could be taken:
  1. Allow temporary account assumption that we could use
  2. We would than generate temporary API connection with a key/token that we will use for testing purpose.
  3. Run performance/load tests
  4. Report back and delete temporary connection we created

0


Perfect, yes please.

Account assumption is turned on and you can test the API connection, please.

 

Still fighting the errors and redoing it manually….

0


Any news? :)

0


Please sign in to leave a comment.

Didn't find what you're looking for?

New post