User Data Function - Couldn't submit your request from Power BI

[ngantd]

Hi,

I've currently created a dashboard that used an User data function to allow user to input their url. The dashboard was working fine on the first day, but since then, I haven't been able to submit any input. I'm now receiving the following message:

User data function: 'pbi_user_input_demo' invocation failed. Service is unable to process the request at this time, please try again later.

In the backend (the function editor), I've tested the function and it frequently throws a similar error. 

{
"functionName": "pbi_user_input_demo",
"invocationId": "00000000-0000-0000-0000-000000000000",
"status": "AzFuncServiceUnavailable",
"errors": [
{
"errorCode": "WorkloadException",
"subErrorCode": "ServiceUnavailable",
"message": "User data function: 'pbi_user_input_demo' invocation failed. Service is unable to process the request at this time, please try again later."
}
]
}

I believe this is an issue with the Azure Function and was supposed to be temporary, but it has now persisted for a week. I wonder if anything I can do to make it work?

I've read that a potential solution for the Azure Function is to switch to the Premium Plan or Dedicated Plan to avoid cold starts. However, I don't have the necessary permissions to access the Azure Function directly, so this will not work. And since the user data function was designed for Power BI users, I believe the solution should not be that complicated.

Thanks

[v-veshwara-msft]

Hi @ngantd ,

Just checking in to see if you query is resolved and if any responses were helpful.
Otherwise, feel free to reach out for further assistance.

Thank you.

[ngantd]

It still persists, and upgrading the Az function plan costs more than we expected, so I'm now testing Power Apps.

It's very strange, though, the user data function works perfectly on my trial account without any Azure config.

[v-veshwara-msft]

Hi @ngantd ,
Thanks for the update.

Since this is still in preview, the behavior can differ between environments, which may explain why it works in your trial but not in production without additional configuration.

Testing with Power Apps is a valid approach while you explore alternatives. Please keep us updated on your progress with Power Apps, and share here if the issue changes or gets resolved, for the benefit of others following this thread.

Thank you.

[v-veshwara-msft]

Hi @ngantd ,
Just checking in to see if you had any progress with Power Apps, or if the issue with the User Data Function has changed since your last update.

Thank you.

[ngantd · Accepted solution]

Thanks for all your helps,

Today, I've rechecked the user data function, and it seems to be in official release now. I'm not entirely sure, but I no longer see preview when creating the function.

So I've tried again but the old item function set is still not working. But when I created a new one, it worked perfectly. I'll update in the next few days to see if the issue appears with this function set.

@v-veshwara-msftRegarding your question about Power Apps, I've created it, and it works fine. I just need approval to deploy it to production, so there's no issue with this approach. It's just too complicated for my work.

Thanks

[v-veshwara-msft]

Hi @ngantd ,
Just following up to ask if the new user data function you created is still working as expected, or if you have noticed any further issues.

Please reach out for further assistance.

Thank you.

[ngantd]

It's working fine now, and I've asked users to use it, no complaints so far.

[v-veshwara-msft]

Hi @ngantd ,
Thanks for sharing the update.

User Data Function was recently in preview, and it is possible that changes were made as part of its release, which might explain why a newly created function is working while the older one is not. Apologies for any confusion earlier regarding its preview status.

It’s also good to know that the Power Apps approach is functioning while you wait for production approval.

Please keep us informed if the new function remains stable or if any issues come up again, as that will help others who may face a similar situation.

Best, 
Vinay.

[rohit1991]

Hi @ngantd 

The error you are seeing is not really from Power BI, it is coming from the Azure Function that your User Data Function depends on. When an Azure Function runs on the Consumption plan, it can take time to start (called a “cold start”), and sometimes Power BI times out with the ServiceUnavailable / WorkloadException error. That is why it may have worked on the first day but started failing later. The best fix is to move the function to a Premium or Dedicated plan, as these do not have cold start issues. Since you mentioned you don’t have access to change the function, you’ll need the owner or admin of the function to update it. If that is not possible, you can try again later, as sometimes the service responds after a delay. Another option is to think about using parameters or What-If tables inside Power BI instead of calling the Azure Function, if the main need is just user input. In short, the problem is with the function service, not your dashboard, and the permanent solution requires a change on the Azure side.

[ngantd]

Thanks for your help. In my scenario, I need to write back user input, and a what-if parameter can't do that.

A Power App is another potential solution, but managing a separate app for a simple task is inefficient. Additionally, as I remember, it requires a different license type to publish an app to production.

I'll try to get support from the team that manages the Azure.

User data function is still preview feature but I expected to be able to use it without any configuration from Azure. Hope this issue is fixed once the feature is officially released.

[v-veshwara-msft]

Hi @ngantd ,
Thanks for following up.

User Data Function is still in preview, and as highlighted by @rohit1991 , the error is coming from the Azure Function that it depends on. Since you do not have access to the Azure resource, reaching out to the team that manages it is the right approach. Cold start behavior on the current plan can cause these issues, and while your observation is correct, they may continue until the feature reaches general availability.

Please update us if your Azure team is able to make any changes or if the issue resolves over time.

Please reach out for further assistance.

Thank you.