The 'ListCallbackUrl' API is not supported by triggers of type 'ServiceProvider' when logic apps trigger run

Diapk Nirval 21

Hi, I have added a blob storage trigger when file is upload and modified and action is Http rest call in logic app workflow.

the problem is that once the file is uploaded in blob storage, automation trigger will fired and executed but below error is given by logic app trigger.

{\"error\":{\"code\":\"ApiNotSupported\",\"message\":\"The 'ListCallbackUrl' API is not supported by triggers of type 'ServiceProvider'.\"}}

Can any one help me on this case or issue?

Kamlesh Kumar 3,861 Reputation points

2022-06-21T18:45:01.073+00:00

Hi @Diapk Nirval ,

We would need more information about the issue, which LA type you are using and is it possible to share the WF screen shot?

Because I tried to replicate the same at my end and it's working fine in Standard as well as consumption LA.

Regards,
Kamlesh Kumar
Diapk Nirval 21 Reputation points

2022-06-21T19:02:53.473+00:00

Hi @Kamlesh Kumar ,

LA type is Standard and below is WF screen shot logic app.

Could you plz check logic apps active log also you will get error in log below is screen shoot.

please help me on this issue ASAP.

Accepted answer

Kamlesh Kumar 3,861 Reputation points

2022-06-22T10:50:39.193+00:00

Thanks @Diapk Nirval for the detailed information.

You can use Consumption Logicapp for this and there it should work.

For standard LA, Yes so this error comes when you use the Trigger Type other than Request, In that case Workflow URL will not generate and in activity log this you see the error event with operation "
Get Web Apps Hostruntime Workflow Trigger Uri". I have highlighted in the below screenshot, But I feel this doesn't stop the process in LogicApp.
Please sign in to rate this answer.

1 person found this answer helpful.
Diapk Nirval 21 Reputation points

2022-06-22T11:59:52.797+00:00

Thanks @Kamlesh Kumar ,

Issue is sorted now...I have changed the LA type to consumption plan and tried same workflow and it's working.

Kamlesh Kumar 3,861 Reputation points

2022-06-22T12:21:20.4+00:00

Glad to know it's working fine in consumption, I have modified my comment and feel free to marks it as Answer, it'll helpful for community members.

Mohsin Memon 30 Reputation points

2023-03-10T04:33:34.1366667+00:00

Hi Kamlesh Kumar,

Is there a way to make this work under Logic App Standard and not consumption ?

Mohsin

NehaRastogi 5 Reputation points

2023-08-21T10:11:04.67+00:00

How to make this to work in 'Standard' logic app? I am using 'Recurrence' trigger and getting same error.

Phillip blackwell 0 Reputation points

2023-08-30T17:24:09.2766667+00:00

It's been a year and people are still experiencing issues with this. SQL triggers and other types of trigger should be even more supported for standard LA.
We can't use a consumption based logic app because we need to use the vnet injection feature of standard.

Anonymous

2023-10-05T12:09:17.2633333+00:00

I'm also experiencing exactly the same issue.

Taelman Stijn 0 Reputation points

2023-11-02T12:26:47.1+00:00

We are experiencing the same problem here, we really need a fix for this
Sign in to comment

1 additional answer

NehaRastogi 5 Reputation points

2023-08-21T10:10:52.8166667+00:00

How to make this to work in 'Standard' logic app? I am using 'Recurrence' trigger and getting same error.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment