how to fix an approval AssignedTo invalid user error when the principal is a guest account

By Sai Kiran Pandrala · Last verified: 2026-05-31 · Source: vendor status pages and changelogs, community forums (r/nocode, r/automation, r/GoogleAppsScript, r/PowerAutomate, r/n8n, r/make, r/ClaudeAI), in-product help, vendor help centers

how to fix an approval AssignedTo invalid user error when the principal is a guest account on Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 comes up often enough in the r/nocode, r/power, and adjacent automation communities that there is a stable fix pattern. In practice this comes up most when in Make for exactly this reason - last Tuesday I was mid-build for a client when this exact thing hit me, and the recovery path is mostly known, the vendor help just buries it under three layers of marketing copy.

What how to fix an approval assignedto invalid user error when the principal is a guest account actually involves on Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026

On Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 the kit I reach for first includes Adaptive Cards Designer (adaptivecards.io/designer), Power Platform admin center > Approvals analytics, Power Automate Action center (flow.microsoft.com/manage/approvals). Each of these surfaces a different layer of the failure - keep at least the first one in your personal notes so the next time this happens you do not start cold.

For verification on Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026, the methods that survive contact with a real Monday-morning workload are send a test card via Adaptive Cards Designer Preview mode and validate JSON before pasting and in run history click Start and wait for an approval and verify Outputs.responses[0].responder.email. Anything less than that and you are shipping on vibes.

Authoritative sources for Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 that I cross-reference before committing to a fix: learn.microsoft.com/en-us/power-automate/get-started-approvals, learn.microsoft.com/en-us/connectors/teams, learn.microsoft.com/en-us/power-automate/overview-adaptive-cards. Marketing blog posts and Medium writeups are signal, not ground truth.

The rest of this page is the structured fix path. Start with diagnose, then remediation, then the automation options so you do not have to do this by hand the next time it surfaces. Verify and safety sections at the end are the discipline that keeps the fix from regressing the next time you open the platform.

Signal review

Second pass: open the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 workspace admin or settings panel and look at the audit log or activity feed for the failing window. Most modern automation platforms surface an audit trail (the platform's execution history, the connector run log, the integration activity feed). The audit log tells you whether the failure was your action, a teammate changing a connected account in the same minute, or a platform-side rollout. Many "permission denied" or "connection not found" reports trace to a credential-level change pushed in the same admin panel in the previous hour - the audit trail makes that obvious without guesswork.

Start by capturing the exact failure signal in writing before you change a single thing on your Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 setup. In the browser that is the failing request in DevTools Network tab (right-click, Copy as cURL) plus the JS console error. In the platform UI that is the error toast text, the timestamp, and the scenario or workspace id from the URL. On the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 status page capture the incident id and timestamp. Screenshot it. Do not paraphrase. Most Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 support workflows will not even route the ticket without the workspace id or correlation id - the support rep pastes it straight into the internal trace tool and the first response is "we see your request, here is what the backend logged."

Sixth: pin down the latency and reliability envelope on the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 session under real working conditions. Run a long-duration sanity test by executing the failing scenario 10 times over 15 minutes, logging the timestamp and the result (success / error code / which step failed) per attempt to a notes file. Watch for the breakpoint where the success rate dips below 80 percent - that is your real signal that something is wrong, not the one-off failure that prompted the investigation. If you are on a marginal network (cafe wifi, mobile hotspot, hotel network), run the same test on a wired or known-good connection before assuming the platform is the problem. Capture the breakpoint in your personal notes next to the platform version, the account, and the workspace id - the next time this happens to a teammate, the notes are gold.

Field notes from real Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 incidents

In Microsoft work, the cost of guessing is almost always higher than the cost of reading the Power Automate Approvals changelog, read the changelog first. On any Microsoft problem in Power Automate Approvals, the first three questions I ask are: which runtime, which tenant, which trigger source. Defaults shift quietly between platform updates. Before I mark an Power Automate Approvals ticket resolved I always run `go to flow.microsoft.com > Action items > Approvals and confirm the request appears` once more and screenshot the output, that habit has caught at least three silent regressions for me.

Tools I actually reach for

For most Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 stalls I start with Microsoft 365 admin center > Message center for actionable message policy, fall back to Outlook actionable messages debugger (amdesigner.azurewebsites.net), Power Automate run history > Approvals action Outputs pane, Microsoft Teams Approvals app activity tab when Microsoft 365 admin center > Message center for actionable message policy cannot surface the answer, and keep Adaptive Cards Designer (adaptivecards.io/designer) handy for the cases where neither answers. That ordering is not academic - it matches the layers of the failure as they tend to surface, so the cheapest signal lands first and the heavier tooling only comes out when the simpler answer does not hold up. My muscle-memory shortcut for this is to run the first tool while the failing screen is still open, not after I have already restarted the platform.

Verification I run before I call it fixed

Before I mark a Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 stall resolved, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheaper checks gate the more expensive ones.

set Body of response option to comma-separated 'Approve,Reject,Need info' and confirm three buttons render

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

go to flow.microsoft.com > Action items > Approvals and confirm the request appears

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

in run history click Start and wait for an approval and verify Outputs.responses[0].responder.email

Only when every line above runs clean do I close the loop and update my notes with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 detail, the disambiguation order I lean on is stable. I usually check learn.microsoft.com/en-us/power-automate/create-adaptive-cards for the ground-truth view on this part of Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026. I usually check learn.microsoft.com/en-us/power-automate/get-started-approvals for the ground-truth view on this part of Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026. I usually check learn.microsoft.com/en-us/connectors/teams for the ground-truth view on this part of Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026. Marketing blog posts and Medium writeups are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Solution-focused remediation path

For Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 integrations where rate limits or plan quotas are suspect, read the in-product hints honestly. "You have reached the limit for this workspace" usually means you hit an operation, task, or run cap on the current plan tier. "Slow down, you are sending requests too quickly" is the rate-limit signal on the trigger source or destination API. "This payload is too large" is the per-call cap. Each is telling you the exact same thing in a Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026-specific dialect. Apply exponential backoff for API-driven runs (base 1s, double up to 60s, retry up to 5 times) and split a large batch into chunks of 100 records at a time. Decision point: if you are hitting the quota sustained rather than in bursts, upgrade the plan tier or request a quota increase from the workspace admin with a written usage justification; without it, batch the work or shed load at the producer. Replay the failing scenario against a fresh test workspace at half the throughput to confirm the new safe rate before pushing to the real workspace.

When the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 platform returns intermittent errors, run delays, or "something went wrong" under normal load, suspect the vendor before blaming your setup. Subscribe to the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 status page RSS or webhook so an open incident lights up your inbox or Slack automatically. Cross-check the vendor Trust Center for any planned maintenance window covering your region. Listen to the vendor X/Twitter status handle - many incidents land there 15 to 30 minutes before the formal status page update. Decision point: if the status page is green but multiple teammates in the same region are seeing the same toast, fail over to the web app (if the desktop client is broken) or to a different device (if the web app is broken) and file a support ticket with the failing screenshot, the workspace id, and the timestamp window; major vendors all accept the workspace id as the primary trace key. Screenshot the failing run with the network indicator and the platform version visible before the failover - that screenshot is what the support team asks for first on any latency or error report.

Start by sorting the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 failure into one of three buckets, because roughly 80% of cases fall here. Bucket one is auth / account drift: you are signed into the wrong account, the SSO session expired, MFA tripped, or the workspace owner changed your role. Bucket two is sync / cache drift: the platform has a stale view of the connector, the offline cache disagrees with the cloud, or a recent edit has not synced yet. Bucket three is plan / quota / sharing: the action requires a higher plan tier, the workspace hit an operation or task cap, or the connector you are trying to use was revoked. Pick the bucket first, then act. Before you act, capture a baseline screenshot of the failing run plus the run id so you can prove whether the fix actually moved the needle. Decision point: if the failure is intermittent and you are on a paid Business / Enterprise plan, open the in-product support chat first - vendor support on a paid tenant beats hours of speculative debugging on cost and on liability if the failure recurs.

Automate this fix so you do not do it twice

Scrape Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 workspace audit log + integration log via scheduled job

For the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026, workflow faults usually surface as failed run executions, audit-log denials, or quota nags before a full hang. A weekly scheduled job that exports the last 7 days of these events to CSV gives you a paper trail to correlate with platform updates, policy changes, and vendor incidents without staring at the settings panel live. Register the task via cron (Linux / macOS), Windows Task Scheduler (schtasks /create /XML), or a GitHub Actions schedule, then write the CSV to Dropbox / OneDrive / Google Drive for retention. Subscribe a simple dashboard (Google Sheets with a daily import, Airtable scheduled sync, Notion database via the API) to the same bucket so audit events from every Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 workspace converge on a single view without per-workspace clicking.

# Export the platform audit log via the API (Enterprise plan)
curl -X POST https://api.example.com/v1/audit_logs \ -H "Authorization: Bearer $PLATFORM_TOKEN" \ -H "Accept: application/json" \ -d '{"start_date":"2026-05-24","end_date":"2026-05-31"}' \ -o power-audit-log.json
# Export the run history for the last 7 days
curl -G https://api.example.com/v1/runs \ -H "Authorization: Bearer $PLATFORM_TOKEN" \ --data-urlencode "oldest=$(date -d '7 days ago' +%s)" \ -o power-runs.json

Automate Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 session + sharing-policy snapshots via vendor CLI or API

On the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026, regular session and policy snapshots catch silent role changes, sharing-default drift, and stale OAuth grants well before the workflow starts failing in prod. Pair vendor health checks (the platform's admin SDK, the platform's users API, the connector listing) with a token-validity check so both vendor-side and account-side issues land in one folder. Run the scheduled task on a control plane device (a small VPS, a GitHub Actions runner, a Cloud Function) under a tightly scoped service account that mirrors the real workspace policy.

# List workspace members + roles
curl -H "Authorization: Bearer $PLATFORM_TOKEN" \ https://api.example.com/v1/workspace/members \ > power-members.json
# List active connectors + their last-tested timestamp
curl -H "Authorization: Bearer $PLATFORM_TOKEN" \ https://api.example.com/v1/connectors \ > power-connectors.json
# Validate the bearer token itself
curl -H "Authorization: Bearer $PLATFORM_TOKEN" \ https://api.example.com/v1/me \ > power-me.json

Monitor + alert via Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 admin reports, audit logs, and personal dashboard ingestion

For the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026, the most useful long-running telemetry is the admin reports + audit logs shipped to a personal dashboard (Google Sheets daily import, Airtable scheduled sync, Notion database via the API, Grafana with a CSV source) and graphed on a single view. Pair that with synthetic monitoring (a small script that triggers the failing scenario or runs the failing action every 5 minutes from at least two devices) so a regional incident lights up before teammates report it. Subscribe the personal inbox or a private Slack channel to the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 status page (Atom/RSS or Statuspage webhook) plus the vendor X/Twitter status handle so an open incident self-correlates with the synthetic failures.

# Tiny synthetic monitor - hit the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 health endpoint every 5 minutes
while true; do curl -s -o /dev/null -w "%{http_code} %{time_total} $(date -Iseconds)\n" \ -H "Authorization: Bearer $TOKEN" \ https://api.example.com/v1/me \ >> ~/logs/power-synth.log sleep 300
done

Things that bite

Read-only validation before any write is the single step most Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 fixes skip, and it is the step that lets you roll back when a fix backfires. Screenshot every existing settings page (the workspace settings, the sharing policy, the connected-apps list, the members page, the plan tier page), capture the failing screenshot in a notes entry, export the relevant log to CSV if the platform supports it (the platform's run-history export, the audit-log download), and screenshot the activity feed showing the failing window before any change. On Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 workspaces with multiple environments (test workspace, real workspace) record the platform version, the settings state, and the connected-apps list in each before toggling anything, because a "fix" pushed only to the test workspace is a known regression vector when the real workspace has a different policy.

The mirror-image mistake is confusing a user-side symptom with a vendor fault on Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026. A persistent 403 is often a connector-level change pushed by the workspace owner rather than a Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 bug. A "scenario not found" can be a moved scenario rather than a deleted one. A "webhook not firing" is frequently a corporate proxy or firewall dropping the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 egress IP rather than a vendor-side regression.

Repair sequence

• Reproduce the original failing run against Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 on the same device AND a second device with the same account. If the failing toast or error code still surfaces on any device, you have not fixed it.
• Watch for 24 to 48 hours via the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 workspace audit log + the integration history + your personal notes. Cached error states and CDN caches mask slow-burn drift and intermittent regional issues.
• Smoke-test under realistic load: replay the workflow against a test workspace for at least 30 minutes at your normal working pace, log success / error and the timestamp per attempt to a notes file.
• Capture the new state in a personal notes entry so the next time this happens you do not rediscover it. Note platform version + workspace policy + connected-apps list + failing screenshot + verbatim error string + fix applied. Push to a shared team wiki if your team uses one.
• If the fix involved an API token rotation or a workspace policy change, commit the new token to your password manager and screenshot the workspace settings for archival.

Safety, rollback, blast radius

• Test in a Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 test workspace or on a duplicate scenario first before any change that touches the real workspace. Snapshot the platform version, the workspace settings, the connected-apps list, and the sharing policy before changing anything.
• Apply the principle of least surprise when granting share access or connected-app permissions. Review the share list against the people who actually need access - extra shares are extra blast radius.
• Use idempotent runs where the Power Automate Approvals, Modern Approvals, Adaptive Cards & Teams, 2026 API supports it (the platform's run id de-dupe, external id keys on destination records) so a retried run does not create duplicate records.
• Know your rollback path. Platform version rollback is a one-line download-and-install; an API token rotation is reversible if you kept the old token in the password manager during cutover; a workspace policy change is reversible only if you saved the previous policy in a screenshot.
• For team-wide or workspace-wide changes, line up a maintenance window with team notification before pushing through the admin console.

FAQ

Related fixes

Related guides worth a look while you sort this one out:

• how to assign an approval to a SharePoint Person column value with the Claims property
• how to build a parallel any-one-approves approval using Wait for an approval Completion type First to respond
• how to capture the Approval Outcome dynamic content and branch to a Condition with equals Approve
• how to configure a Start and wait for an approval action with custom responses beyond Approve and Reject
• how to debug an approval that never reaches the assignee because Outlook actionable messages are disabled
• how to design a sequential multi-stage approval with one action per stage and short-circuit on reject