Feat/2355

[razasaddiqi]

Checklist

• Tests were added/updated according to the feature/bugfix/change made
• Version was rolled according to semver requirements
• API endpoints openapi schema was updated if applicable

Changes

[github-actions]

PR E2E - FAILED

Full report, traces and screenshots

result	FAILED
central run	32487121524
commit	85cfd811
suite	mentor - mode full - env stg1
tested against	prod release 1.126.0 (env was synced to it first)
failed	2
new failures	2

[github-actions]

PR E2E - FAILED

Full report, traces and screenshots

result	FAILED
central run	32544768379
commit	6b7bfd32
suite	mentor - mode full - env stg1
tested against	prod release 1.126.0 (env was synced to it first)
failed	6
new failures	6

[github-actions]

PR E2E - FAILED

Full report, traces and screenshots

result	FAILED
central run	32741304790
commit	6b7bfd32
suite	mentor - mode full - env stg1
tested against	prod release 1.126.0 (env was synced to it first)
failed	6
new failures	6

[github-actions]

PR E2E - FAILED

Full report, traces and screenshots

result	FAILED
central run	32753728343
commit	c696ef6f
suite	mentor - mode full - env stg1
tested against	prod release 1.126.0 (env was synced to it first)
failed	5
new failures	5

[github-actions]

PR E2E - FAILED

Full report, traces and screenshots

result	FAILED
central run	32765571691
commit	a8499f0e
suite	mentor - mode full - env stg1
tested against	prod release 1.126.0 (env was synced to it first)
failed	3
new failures	3

[github-actions]

PR E2E - FAILED

Full report, traces and screenshots

result	FAILED
central run	32787983549
commit	a8499f0e
suite	mentor - mode full - env stg1
tested against	prod release 1.126.0 (env was synced to it first)
failed	3
new failures	3

[github-actions]

PR E2E - skipped

result	skipped
central run	32797288542
commit	a8499f0e
suite	mentor - mode full - env stg1
tested against	prod release 1.126.0 (env was synced to it first)

No test report was produced (result: skipped). The run did not finish a suite — usually because another PR's run took the shared environment, a newer commit/label superseded this one, or it was abandoned before completing. This says nothing about your code.

Re-trigger it yourself: comment /retest (or /retest <spec> to re-run a single file in minutes). /status shows the queue. (Avoid Re-run jobs — that replays the old merge ref instead of recomputing it against current main.)

Last completed run for this PR: report — still valid unless this PR has changed since.

[razasaddiqi]

/retest

[github-actions]

No description provided.

[github-actions]

Re-running the full suite — requested by @razasaddiqi

Expect ~40–50 min plus any queue wait. /status for progress, /cancel to stop it.

Next time: /retest <spec> re-runs a single file in minutes.

[github-actions]

PR E2E - FAILED

Full report, traces and screenshots

result	FAILED
central run	32801571167
commit	a8499f0e
suite	mentor - mode full - env stg1
tested against	prod release 1.126.0 (env was synced to it first)
failed	2
new failures	2

[github-actions]

PR E2E - FAILED

Full report, traces and screenshots

result	FAILED
central run	32879298671
commit	d88c69ea
suite	mentor - mode selective - env stg1
tested against	prod release 1.126.0 (env was synced to it first)
failed	2
new failures	2

[github-actions]

PR E2E - FAILED

Full report, traces and screenshots

result	FAILED
central run	32891744732
commit	d88c69ea
suite	mentor - mode selective - env stg1
tested against	prod release 1.126.0 (env was synced to it first)
failed	1
new failures	1

[bnsoni]

/retest

[github-actions]

⚠️ Could not start the run

The run-tests label was recycled but no run appeared. Please remove the label and add it
back by hand — that always works.

A maintainer should check the handler's PAT: a label change made with GITHUB_TOKEN
raises no events, so the trigger silently does nothing.