# \#in-progress **URL:** https://developer.sailpoint.com/discuss/tag/in-progress/652.md [Latest](https://developer.sailpoint.com/discuss/latest.md) · [Categories](https://developer.sailpoint.com/discuss/categories.md) · [Tags](https://developer.sailpoint.com/discuss/tags.md) --- ## [Email Template V1 date format timezone issues - Certification Reassignment](https://developer.sailpoint.com/discuss/t/email-template-v1-date-format-timezone-issues-certification-reassignment/37714)
**Author:** [@gmilunich](https://developer.sailpoint.com/discuss/u/gmilunich)\ **Replies:** 9\ **Last updated:** [June 24, 2024, 7:40pm UTC](https://developer.sailpoint.com/discuss/t/email-template-v1-date-format-timezone-issues-certification-reassignment/37714 "2024-06-24T19:40:51Z")
Ok, this seems to come up regulatly, but without a resolution, so I wanted to propose it again, and add some specifics details for it, as well as show some anomalies I am seeing with this in my Ambassador tenant. First … --- ## [/beta/work-items endpoints response header defaults to application/octet-stream instead of application/json](https://developer.sailpoint.com/discuss/t/beta-work-items-endpoints-response-header-defaults-to-application-octet-stream-instead-of-application-json/36350)
**Author:** [@nsorlien](https://developer.sailpoint.com/discuss/u/nsorlien)\ **Replies:** 2\ **Last updated:** [June 7, 2024, 6:02pm UTC](https://developer.sailpoint.com/discuss/t/beta-work-items-endpoints-response-header-defaults-to-application-octet-stream-instead-of-application-json/36350 "2024-06-07T18:02:11Z")
A weird quirk with the /beta/work-items APIs in general: unless you explicitly set the Accept request header to application/json, the Content-Type of the response is application/octet-stream. This breaks Pretty formattin… --- ## [GET /workflows incorrectly reporting 0 executions](https://developer.sailpoint.com/discuss/t/get-workflows-incorrectly-reporting-0-executions/37915)
**Author:** [@sup3rmark](https://developer.sailpoint.com/discuss/u/sup3rmark)\ **Replies:** 3\ **Last updated:** [March 28, 2024, 6:12pm UTC](https://developer.sailpoint.com/discuss/t/get-workflows-incorrectly-reporting-0-executions/37915 "2024-03-28T18:12:00Z")
I have a Workflow in my production environment that shows over 2000 Successful Runs and an Error Rate of 0.84%. When I make a GET call to the List Workflows endpoint ({{baseUrl}}/workflows), it says it’s run 0 times. … --- ## [GET /api/source/connections](https://developer.sailpoint.com/discuss/t/get-api-source-connections/20499)
**Author:** [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\ **Replies:** 0\ **Last updated:** [November 6, 2023, 6:44pm UTC](https://developer.sailpoint.com/discuss/t/get-api-source-connections/20499 "2023-11-06T18:44:50Z")
The replacement for this API will be available by the end of March, 2024. To give users enough time to migrate to the public replacement, this API’s shutoff date has been extended to August 30th. --- ## [GET /api/passwordSummary/detailed](https://developer.sailpoint.com/discuss/t/get-api-passwordsummary-detailed/15432)
**Author:** [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\ **Replies:** 0\ **Last updated:** [August 2, 2023, 2:31pm UTC](https://developer.sailpoint.com/discuss/t/get-api-passwordsummary-detailed/15432 "2023-08-02T14:31:34Z")
The replacement for this API will be available by the end of March, 2024. To give users enough time to migrate to the public replacement, this API’s shutoff date has been extended to June 14th. --- ## [GET /api/passwordSummary/brief](https://developer.sailpoint.com/discuss/t/get-api-passwordsummary-brief/33046)
**Author:** [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\ **Replies:** 0\ **Last updated:** [March 1, 2024, 7:56pm UTC](https://developer.sailpoint.com/discuss/t/get-api-passwordsummary-brief/33046 "2024-03-01T19:56:22Z")
The replacement for this API will be available by the end of March, 2024. To give users enough time to migrate to the public replacement, this API’s shutoff date has been extended to June 14th. --- ## [POST /api/challenge/set](https://developer.sailpoint.com/discuss/t/post-api-challenge-set/33040)
**Author:** [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\ **Replies:** 0\ **Last updated:** [March 1, 2024, 7:53pm UTC](https://developer.sailpoint.com/discuss/t/post-api-challenge-set/33040 "2024-03-01T19:53:53Z")
The replacement for this API will be available by the end of March, 2024. To give users enough time to migrate to the public replacement, this API’s shutoff date has been extended to June 14th. --- ## [POST /api/challenge/update](https://developer.sailpoint.com/discuss/t/post-api-challenge-update/33039)
**Author:** [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\ **Replies:** 0\ **Last updated:** [March 1, 2024, 7:53pm UTC](https://developer.sailpoint.com/discuss/t/post-api-challenge-update/33039 "2024-03-01T19:53:19Z")
The replacement for this API will be available by the end of March, 2024. To give users enough time to migrate to the public replacement, this API’s shutoff date has been extended to June 14th.