# Retrigger ServiceDesk Ticket Creation **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** sailpoint-identity-security\ **Created:** [May 17, 2024, 3:32pm UTC](https://developer.sailpoint.com/discuss/t/retrigger-servicedesk-ticket-creation/57132 "2024-05-17T15:32:50Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![maheshtare](https://avatars.discourse-cdn.com/v4/letter/m/aca169/32.png) [@maheshtare](https://developer.sailpoint.com/discuss/u/maheshtare)\ **Post date:** [May 17, 2024, 3:32pm UTC](https://developer.sailpoint.com/discuss/t/retrigger-servicedesk-ticket-creation/57132/1 "2024-05-17T15:32:50Z")
Hi Guys, We are generating ServiceNow tickets via Service Desk integration for delimited file application access reviews (certifications). However, ticket creation failed due to connectivity issue between SailPoint & ServiceNow. How we can re-trigger ticket creation for such failures. Regards, Mahesh Tare ---
**Author:** ![sarvar\_nasirov](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sarvar_nasirov/32/10906_2.png) [@sarvar\_nasirov](https://developer.sailpoint.com/discuss/u/sarvar_nasirov)\ **Post date:** [May 17, 2024, 9:01pm UTC](https://developer.sailpoint.com/discuss/t/retrigger-servicedesk-ticket-creation/57132/2 "2024-05-17T21:01:24Z")
++ Interested as well. Every time I update the integration with another source the authentication (password) has to be fixed(reentered) as well. Otherwise there many FAILED events in provisioning ---
**Author:** ![mcheek](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mcheek/32/23705_2.png) [@mcheek](https://developer.sailpoint.com/discuss/u/mcheek)\ **Post date:** [May 18, 2024, 1:12am UTC](https://developer.sailpoint.com/discuss/t/retrigger-servicedesk-ticket-creation/57132/3 "2024-05-18T01:12:27Z")
Try sending a revoke access request through the access request API ---
**Author:** ![sarvar\_nasirov](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sarvar_nasirov/32/10906_2.png) [@sarvar\_nasirov](https://developer.sailpoint.com/discuss/u/sarvar_nasirov)\ **Post date:** [May 18, 2024, 4:43am UTC](https://developer.sailpoint.com/discuss/t/retrigger-servicedesk-ticket-creation/57132/4 "2024-05-18T04:43:32Z")
I thought he meant to retry on failure. Maybe a workflow that triggers on source’s “provisioningResult”:“failure” ---
**Author:** ![maheshtare](https://avatars.discourse-cdn.com/v4/letter/m/aca169/32.png) [@maheshtare](https://developer.sailpoint.com/discuss/u/maheshtare)\ **Post date:** [May 20, 2024, 8:57am UTC](https://developer.sailpoint.com/discuss/t/retrigger-servicedesk-ticket-creation/57132/5 "2024-05-20T08:57:26Z")
Hi @mcheek, Thanks for the response. Is there a way ISC can automatically re-trigger ticket creation for failures in provisioning? We are using OOTB Service Desk Integrations not the workflows. ---
**Author:** ![maheshtare](https://avatars.discourse-cdn.com/v4/letter/m/aca169/32.png) [@maheshtare](https://developer.sailpoint.com/discuss/u/maheshtare)\ **Post date:** [May 22, 2024, 10:34am UTC](https://developer.sailpoint.com/discuss/t/retrigger-servicedesk-ticket-creation/57132/6 "2024-05-22T10:34:10Z")
Hi All, Can anyone help on this. Our problem is ServiceNow ticket creation for revoke access operation triggered via certifications has failed. Now, how to re-trigger the ticket creation for the same request? Is there an API available for this? can ServiceDesk Integration automatically do this? ---
**Author:** ![baoussounda](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/baoussounda/32/13095_2.png) [@baoussounda](https://developer.sailpoint.com/discuss/u/baoussounda)\ **Post date:** [May 29, 2024, 12:14pm UTC](https://developer.sailpoint.com/discuss/t/retrigger-servicedesk-ticket-creation/57132/7 "2024-05-29T12:14:04Z")
Hi @maheshtare, According to this api [update-status-check-details | SailPoint Developer Community](https://developer.sailpoint.com/docs/api/v3/update-status-check-details) For SDIM integration, after **provisioningMaxStatusCheckDays** , IDN/ISC will ignore checking status and recreate another ticket. And in my experience if ticket creation is failed, IDN/ISC retry the creation on Identity resfresh i don’t know this is applicable on certification revocation. But for me if ISC/IDN not retry after several the fastest way to resolve the problem is to submit revocation access by api as you say. You can download your certification “Remediation status report” for see what revocation for Service Desk are not completed and then submit revocation by adding certification and certifier as reference in comment. ---
**Author:** ![maheshtare](https://avatars.discourse-cdn.com/v4/letter/m/aca169/32.png) [@maheshtare](https://developer.sailpoint.com/discuss/u/maheshtare)\ **Post date:** [May 29, 2024, 1:10pm UTC](https://developer.sailpoint.com/discuss/t/retrigger-servicedesk-ticket-creation/57132/8 "2024-05-29T13:10:05Z")
Hi @baoussounda, Really appreciate your response on this. ISC is not re-triggering the ticket creation on Identity Refresh, it’s been 7 days now. I have discovered the option to submit the revoke\_access request via API but it doesn’t have requester details like we can’t add specific requester (i.e. original certification reviewer) details in the request body. ---
**Author:** ![baoussounda](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/baoussounda/32/13095_2.png) [@baoussounda](https://developer.sailpoint.com/discuss/u/baoussounda)\ **Post date:** [May 29, 2024, 1:25pm UTC](https://developer.sailpoint.com/discuss/t/retrigger-servicedesk-ticket-creation/57132/9 "2024-05-29T13:25:05Z")
> [@maheshtare](#): > > iginal cer @maheshtare by default request are who Personnal access token is used for api call. You can’t submit a request for another person. You have two options : - In the request comment you can all reference of certifications campaign. - You have clientMetadata also ( [create-access-request | SailPoint Developer Community](https://developer.sailpoint.com/docs/api/v3/create-access-request)) ![image](https://global.discourse-cdn.com/sailpoint/original/2X/5/54159514f144432bcac8ac228d93f58f9abb5396.png) With that you can arbitrary add key : value, this key value are not used but it will present always in you request for audit or more context and it is not visible in the ui. ---
**Author:** ![mcheek](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mcheek/32/23705_2.png) [@mcheek](https://developer.sailpoint.com/discuss/u/mcheek)\ **Post date:** [May 29, 2024, 2:44pm UTC](https://developer.sailpoint.com/discuss/t/retrigger-servicedesk-ticket-creation/57132/10 "2024-05-29T14:44:45Z")
> [@baoussounda](#): > > You can’t submit a request for another person If your user tied to the token has ORG\_ADMIN, you can ---
**Author:** ![baoussounda](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/baoussounda/32/13095_2.png) [@baoussounda](https://developer.sailpoint.com/discuss/u/baoussounda)\ **Post date:** [May 29, 2024, 3:19pm UTC](https://developer.sailpoint.com/discuss/t/retrigger-servicedesk-ticket-creation/57132/11 "2024-05-29T15:19:55Z")
@mcheek he want to submit multiple revovation by using access requests endpoint. As administrator of ISC he’s an administrator, by " You can’t submit a request for another person" i will mean with his administrator token he can’t submit request by specifing a requester for each certifier. in the documentation i do not see a requester paamet when submit an access request endpoint. Do you once test that ? ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [July 28, 2024, 3:20pm UTC](https://developer.sailpoint.com/discuss/t/retrigger-servicedesk-ticket-creation/57132/12 "2024-07-28T15:20:24Z")
Closed on July 28, 2024, 3:20pm UTC This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.