microsoft / microsoft/PowerPlatformConnectors

[BUG] Mime Automation connector suddenly throws ResponseSwaggerSchemaValidationFailure

Open
#3,728 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
1.3k
Forks
1.5k
Avg merge
5d 15h
Merged PRs (30d)
11

Description

Type of Connector

Independent Publisher Connector

Name of Connector

Mime Automation

Describe the bug

When using the "Extract files from a EML-encoded file" action of the Mime Automation connector it suddenly fails with the follwowing issue...

ResponseSwaggerSchemaValidationFailure. The API 'mimeautomationip' returned an invalid response for workflow operation 'Extract_files_from_a_base64-encoded_EML_file' of type 'OpenApiConnection'. Error details: 'The API operation 'ExtractFilesFromEml' requires the property 'body' to be of type 'Array' but is of type 'String'.'

The action always throws this error, although nothing was changed in the backend. Even in Postman its working as usual.

Is this a security bug?

No, this is not a security bug

What is the severity of this bug?

Severity 1 - Connector is broken or there's a very serious issue

To Reproduce
  1. Create a new Power Automate flow.
  2. Use "Manually trigger a flow" trigger
  3. Initialize variable of type string with the following content of this file:
    https://github.com/acieslik/PowerPlatformConnectors/raw/refs/heads/dev/.vscode/bug1
  4. Add Mime Automation => "Extract files from a base64-encoded EML file" action
  5. In the Content property pass in the Initialize variable from above
  6. Run the flow
  7. It will fail.
Expected behavior

The output of the "Extract files from a base64-encoded EML file" action should be as documented here:
https://learn.microsoft.com/en-us/connectors/mimeautomationip/#array-of-mimeattachment
An array with 3 properties, File Name, Mime Type and Content

Environment summary

Run it on any PowerPlatform environment that supports PowerAutomate flow creation and execution

Additional context

The issue appeared suddenly without having changed anything in the API on the backend side.
With Postman we can execute the API successfully.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Mime Automation connector's "Extract files from a base64-encoded EML file" action and reproduce the failure using the seven steps in the issue. Compare the connector's declared response with the successful Postman response and the documented array of MIME attachments; done means the Power Automate action returns that array instead of a schema-validation error.

Written by the indexing model from the issue text.

Assessment

Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.