[BUG] Issue: x-ms-trigger-value not working

Type of Connector

Custom Connector

Name of Connector

Maximizer Connector

Describe the bug

Hi Everyone,

I am trying to implement a polling trigger.
But the polling trigger didn't get the x-ms-trigger-value in next polling API call.

May I know if the connector has this feature?
And what I am doing wrong?

The swagger.json is attached.
And the path of the trigger is "/api/Lead/tirgger/updated".
apiDefinition.swagger.json

Is this a security bug?

No, this is not a security bug

What is the severity of this bug?

Severity 2 - One or more important connector features are down

To Reproduce

create the custom connector using CLI paconn and try the trigger.

Expected behavior

Some int value should pass into "state" in the next polling.

Environment summary

Install Method:
cli paconn in window

CLI version (paconn --version) :
0.0.20
Python (Windows) 3.10.11 (tags/v3.10.11:7d4cc5a, Apr 5 2023, 00:38:17) [MSC v.1929 64 bit (AMD64)]

OS version: windows server 2016

Shell Type (e.g. bash, cmd.exe, Bash on Windows): cmd.exe

Additional context

na

Start by inspecting the attached apiDefinition.swagger.json, especially the polling trigger at /api/Lead/tirgger/updated, and reproduce it with paconn CLI 0.0.20. Trace whether x-ms-trigger-value is supported for this custom connector and why the state value is absent from the next polling call. Done means the behavior is fixed or the supported limitation and required configuration are documented.