New Execute Command not working on archive .mfunction

Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response

Could you please provide more details or/and media files. As such we have no repro of this issue.

Also, just a reminder, to make your bug report as effective as possible, please try and include the following steps to reproduce the problem:

Steps to Reproduce:
1.
2.
3.

Observed Results:
(Briefly describe what happens)

Expected Results:
(Briefly describe what should happen)

If your ticket does not look like the example given here, then it's likely to be closed as incomplete.

This ticket will automatically reopen when you reply.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

1. New "EXECUTE" command syntaxes don't seem to work in .mfunction files

2. Example: /execute as @a [tag=adventure] run scoreboard players set @a [tag=adventure] adventure 0

It should work for all players tagged "adventure" would get Adventure score 0

3. This command doesn't work when inside function files.
It seems to me that the new "EXECUTE AS ..." syntax was not included to work in mfunction files

I think your behavior pack manifest.json is not set min_engine_version.

try this write

{
    "format_version": 2,
    "header": {
    "uuid": "e9c5a9be-1cfc-4a74-9f70-9213bab62091",
    "name": "Math_new",
    "version": [0, 0, 1],
    "description": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    "min_engine_version":[1,19,10]
     },
    "modules": [
      {
        "description": "子资源包简介",
        "version": [0, 0, 1],
        "uuid": "14d5fb6b-ef0a-47e5-8a98-d615709c1a03",
        "type": "data"
      }
    ]
}

@Missing244 That doesn't work. I tried updating the min_engine version in the preview edition to try and fix my own pack but it doesn't change anything. Content log errors still display, and the functions don't load.

Wait, I just tried again the following day, and it's fixed???

It works for me, probably the manifest file was broken when reporting the bug. Resolving for now, but please create a new issue if this occurs once more.