Answered

PVA post adaptive card and wait for response returns no body/output after submitting form. [Bug]

(3) Share

Report

Posted on by experienced_pva

Hello all,

I am building a PVA and using Adaptive Card to send form on MS Teams to our users. This feature is still in (preview) and was working for past few weeks. Suddenly, today when I sent a form and user submitted the form, I got no output/body.

Click to download has no data except some json below. (Replaced id as 0 for security reasons)

{"headers":{"Transfer-Encoding":"chunked","Host":"prod-223.westeurope.logic.azure.com","X-Forwarded-For":"0.0.0.0","traceparent":"00000000000000000","Request-Id":"|0000000000000000","Content-Type":"application/json; charset=utf-8","Content-Length":"0"}}

Funny thing is , the same is working when I send the form as Flow Bot but not working when I send it as Power Virtual Agent (Preview).

Seems like Microsoft is working on something and broke this feature as still in

Any solutions ?

Categories:

Building Copilot Studio chatbots in Microsoft Teams

I have the same question (0)

All responses (6)

Answers (1)

Sort by

terzogenito 12 on at

Like (1)

Report
Copy link

Link copied!

Seeing the same behavior. Hoping for a fix from Microsoft.

Was this reply helpful? Yes No
Chris0815 6 on at

Like (1)

Report
Copy link

Link copied!

I have exactly the same issue. Lets see when it get fixed.

Was this reply helpful? Yes No
MarkusSchneideG 10 on at

Like (1)

Report
Copy link

Link copied!

Same problem 😞

Was this reply helpful? Yes No
NarianN 27 on at

Like (1)

Report
Copy link

Link copied!

@experienced_pva do you know if there's an open issue about this and if Microsoft is looking into it? I'd like to keep track of when this will be resolved as I am also experiencing the same issues.

Was this reply helpful? Yes No
experienced_pva 45 on at

Like (1)

Report
Copy link

Link copied!

@NarianN I got this below update from Microsoft

Apologies for any inconveniencies this might have cause your business and development processes.

When we have connectors in preview, the issue is that we as support team does not have detailed information on connectors in preview, what we do is we share feedback from users with the Product Group team, to help improve the connector. For now, we cannot give you a time frame in which this will be fully available as a full version to be used in production. The only information is that the connector is in test phase and under monitoring.

Please let me know if I was able to answer your question. We hope this would be improved soon hopefully.
The best approach at the moment is to find another approach to fix the issue.

Since this is still in preview, I was able to confirm that it a known issue that was raised by several users from different regions including Germany and United Arab Emirates (UAE) regions, as we are seeing a rising number of support related cases.

As confirm by the PG team, this is the same behaviour for both standalone PVA chatbot or PVA in Teams as it depends on the regions where the datacentre is hosted. There is list of regions that would be experiencing the error

Currently we do not have an ETA on this, so we don’t know when this would be fixed. The only work around now is to use a different and supported Dataverse environment location and register the chatbot in it.
If you want to use PVA in a Dataverse for Teams(D4T) environments and given that these are created by default in the tenant’s location, you would need to change the tenant’s location to an appropriate region.

Was this reply helpful? Yes No
Verified answer

experienced_pva 45 on at

Like (1)

Report
Copy link

Link copied!

Power Virtual Agents - Adaptive Cards associated with a flow returning incomplete data from PVA bots
ID: FL525018

Status
Service Restored
Impacted services
Microsoft Power Automate
Details
Title: Power Virtual Agents - Adaptive Cards associated with a flow returning incomplete data from PVA bots
User impact: Users may have observed inaccurate data when receiving Adaptive Cards sent by Power Virtual Agents.
Final Status: We have completed deployment of the hotfix and confirmed via diagnostic review that Adaptive Card data is accurate, mitigating the issue.
Incident Start Time: Friday, February 17, 2023, at 12:45 AM UTC
Incident End Time: Friday, March 10, 2023, at 12:33 AM UTC
Preliminary Root Cause: A code regression was introduced in a recent service update to the portion of the infrastructure supporting Adaptive Card flow operations.
Next Steps: We're reviewing our service update configuration procedures to find ways to prevent this problem from happening again.
This is the final update on the incident.

Was this reply helpful? Yes No