@camunda/e2e-test-suite 0.0.1231 → 0.0.1233

package/dist/pages/8.10/ModelerCreatePage.d.ts

@@ -225,6 +225,7 @@ declare class ModelerCreatePage {
     embedForm(formName: string): Promise<void>;
     openDetailsPanelIfCollapsed(): Promise<void>;
     fillStartEventVariablesForDocHandling(zeebeUrl: string, zeebeClientId: string, zeebeClientSecret: string): Promise<void>;
+    private expandOutputMappingEntry;
     fillZeebeClientId(clientId: string): Promise<void>;
     fillZeebeSecretValue(zeebeSecret: string): Promise<void>;
     fillZeebeRestValue(zeebeUrl: string): Promise<void>;

package/dist/pages/8.10/ModelerCreatePage.js

@@ -1856,11 +1856,35 @@ class ModelerCreatePage {
         await this.fillZeebeClientId(zeebeClientId);
         await (0, sleep_1.sleep)(1000);
     }
+    // Each Output mapping row is a collapsible properties-panel entry whose
+    // header *toggles* on click, so a single blind click is not idempotent: when
+    // the panel re-renders while the click is in flight — it does, right after
+    // the preceding FEEL editor commits its value — the entry ends up collapsed
+    // again and its editor keeps a zero-size box. That is what reported
+    // `expect(#bio-properties-panel-StartEvent_1-output-2-source div)
+    // .toBeVisible()` timing out with "unexpected value hidden" for a full 60s
+    // while the trace screenshot showed zeebeRestAdress and zeebeSecret open and
+    // zeebeClientId collapsed. Ask for the state instead of assuming it: only
+    // click while the editor is still hidden, and re-check after each click.
+    async expandOutputMappingEntry(header, editor) {
+        const maxAttempts = 5;
+        for (let attempt = 0; attempt < maxAttempts; attempt++) {
+            if (await editor.isVisible().catch(() => false)) {
+                return;
+            }
+            await header.click();
+            const opened = await editor
+                .waitFor({ state: 'visible', timeout: 15000 })
+                .then(() => true)
+                .catch(() => false);
+            if (opened) {
+                return;
+            }
+        }
+        await (0, test_1.expect)(editor).toBeVisible({ timeout: 60000 });
+    }
     async fillZeebeClientId(clientId) {
-        await this.zeebeClientIdVariable.click();
-        await (0, test_1.expect)(this.variableAssignmentValueTextboxThirdVariable).toBeVisible({
-            timeout: 60000,
-        });
+        await this.expandOutputMappingEntry(this.zeebeClientIdVariable, this.variableAssignmentValueTextboxThirdVariable);
         await this.variableAssignmentValueTextboxThirdVariable.click();
         await (0, sleep_1.sleep)(1000);
         await this.variableAssignmentValueTextboxThirdVariable.fill('');
@@ -1868,10 +1892,7 @@ class ModelerCreatePage {
         await (0, test_1.expect)(this.variableAssignmentValueTextboxThirdVariable).toHaveText(clientId);
     }
     async fillZeebeSecretValue(zeebeSecret) {
-        await this.zeebeSecretVariable.click();
-        await (0, test_1.expect)(this.variableAssignmentValueTextboxSecondVariable).toBeVisible({
-            timeout: 60000,
-        });
+        await this.expandOutputMappingEntry(this.zeebeSecretVariable, this.variableAssignmentValueTextboxSecondVariable);
         await this.variableAssignmentValueTextboxSecondVariable.click();
         await (0, sleep_1.sleep)(1000);
         await this.variableAssignmentValueTextboxSecondVariable.fill('');
@@ -1879,10 +1900,7 @@ class ModelerCreatePage {
         await (0, test_1.expect)(this.variableAssignmentValueTextboxSecondVariable).toHaveText(zeebeSecret);
     }
     async fillZeebeRestValue(zeebeUrl) {
-        await this.zeebeRestAddressVariable.click();
-        await (0, test_1.expect)(this.variableAssignmentValueTextbox).toBeVisible({
-            timeout: 60000,
-        });
+        await this.expandOutputMappingEntry(this.zeebeRestAddressVariable, this.variableAssignmentValueTextbox);
         await this.variableAssignmentValueTextbox.click();
         await (0, sleep_1.sleep)(1000);
         await this.variableAssignmentValueTextbox.fill('');

package/dist/pages/8.10/OptimizeCollectionsPage.js

@@ -33,8 +33,10 @@ class OptimizeCollectionsPage {
             .or(page.getByRole('button', { name: 'Collection', exact: true }));
         this.modalCloseButton = page.locator('button').filter({ hasText: /^Close$/ });
         this.processReport = page.getByText('Process Report').first();
+        // See OptimizeHomePage: Optimize's Design System navigation moved this
+        // link out of the top banner into the left sidebar.
         this.collectionsLink = page
-            .getByRole('banner')
+            .getByRole('navigation', { name: 'Main navigation' })
             .getByRole('link', { name: 'Collections' });
         this.collectionNameInput = page
             .getByRole('dialog')

package/dist/pages/8.10/OptimizeDashboardPage.js

@@ -7,7 +7,13 @@ class OptimizeDashboardPage {
     filterTable;
     constructor(page) {
         this.page = page;
-        this.filterTable = page.getByPlaceholder('Filter table');
+        // Optimize's Design System EntityList replaced the Carbon table toolbar
+        // search (placeholder "Filter table") with a plain input whose placeholder
+        // is the `home.search.name` translation, "Search for name...". With the
+        // old placeholder `clickFilterTable` waited out its 120s on every one of
+        // the five attempts, which is what reported "Process link in Optimize
+        // assertion failed after 5 attempts".
+        this.filterTable = page.getByPlaceholder(/Search for name/i);
     }
     async clickFilterTable() {
         await this.filterTable.click({ timeout: 120000 });

package/dist/pages/8.10/OptimizeHomePage.js

@@ -31,9 +31,19 @@ class OptimizeHomePage {
     filterTableInput;
     constructor(page) {
         this.page = page;
-        this.filterTableInput = page.getByPlaceholder('Filter table');
+        // Optimize's Design System EntityList replaced the Carbon table toolbar
+        // search (placeholder "Filter table") with a plain input whose placeholder
+        // is the `home.search.name` translation, "Search for name...". Matching on
+        // the old placeholder resolved to nothing, so `filterTableToProcess` below
+        // silently fell through and every polling round asserted against the
+        // unfiltered — and now paginated — definition table.
+        this.filterTableInput = page.getByPlaceholder(/Search for name/i);
+        // The same navigation rollout moved Dashboards/Collections out of the top
+        // banner into a left sidebar (`<nav aria-label="Main navigation">`), and
+        // the legacy banner navigation was deleted outright, so a banner-scoped
+        // link can never resolve again.
         this.collectionsLink = page
-            .getByRole('banner')
+            .getByRole('navigation', { name: 'Main navigation' })
             .getByRole('link', { name: 'Collections' });
         this.dashboardLink = page.getByRole('link', { name: 'Dashboards' });
         this.modalCloseButton = page.locator('button').filter({ hasText: /^Close$/ });

package/dist/pages/8.8/FormJsPage.js

@@ -4,6 +4,7 @@ exports.FormJsPage = void 0;
 const test_1 = require("@playwright/test");
 const sleep_1 = require("../../utils/sleep");
 const ProcessApplicationPage_1 = require("./ProcessApplicationPage");
+const sessionRecovery_1 = require("../../utils/sessionRecovery");
 class FormJsPage {
     page;
     processApplicationPage;
@@ -171,6 +172,10 @@ class FormJsPage {
         });
     }
     async clickDeployButton() {
+        // ensureStageCluster navigates away and back before every deploy, so the
+        // action bar this button lives in may belong to a page that never
+        // rendered. Recover before spending the click budget on it.
+        await (0, sessionRecovery_1.recoverStuckModelerLogin)(this.page);
         await this.deployButton.click({ timeout: 60000 });
     }
     async clickDeploySubButton() {

package/dist/pages/8.8/ModelerCreatePage.js

@@ -6,6 +6,7 @@ const sleep_1 = require("../../utils/sleep");
 const clickLocatorWithRetry_1 = require("../../utils/assertionHelpers/clickLocatorWithRetry");
 const ConnectorMarketplacePage_1 = require("./ConnectorMarketplacePage");
 const ProcessApplicationPage_1 = require("./ProcessApplicationPage");
+const sessionRecovery_1 = require("../../utils/sessionRecovery");
 class ModelerCreatePage {
     page;
     processApplicationPage;
@@ -583,6 +584,12 @@ class ModelerCreatePage {
         await (0, test_1.expect)(this.viewProcessLink).toBeHidden({ timeout: 30000 });
     }
     async clickStartInstanceMainButton() {
+        // ensureStageCluster runs immediately before this on every runProcessInstance
+        // attempt and navigates twice, so the diagram's action bar may belong to a
+        // page Modeler never rendered. Without this, each of the 10 retries burned
+        // 60s of probes here and the run surfaced as "View process instance" never
+        // appearing -- which reads as a failed deploy rather than a dead page.
+        await (0, sessionRecovery_1.recoverStuckModelerLogin)(this.page);
         if (await this.startInstanceMainButton.isVisible({ timeout: 30000 })) {
             await this.startInstanceMainButton.click({ timeout: 30000 });
         }
@@ -754,6 +761,11 @@ class ModelerCreatePage {
         await this.nameInput.fill(name, { timeout: 60000 });
     }
     async clickDiagramBreadcrumb() {
+        // Reached straight after opening a diagram, so the navigation that got us
+        // here is the one Modeler can answer with its hung /login. The breadcrumb
+        // never renders there, and at 10s this was the first thing to notice --
+        // as "breadcrumb not found", which says nothing about the real cause.
+        await (0, sessionRecovery_1.recoverStuckModelerLogin)(this.page);
         await this.diagramBreadcrumb.click({ timeout: 10000 });
     }
     // Opening the breadcrumb menu leaves the pointer on the breadcrumb button,
@@ -1631,6 +1643,7 @@ class ModelerCreatePage {
     }
     async fillStartEventVariablesForDocHandling(zeebeUrl, zeebeClientId, zeebeClientSecret) {
         console.log(`URL: ${zeebeUrl}, ClientId: ${zeebeClientId}, Secret: ${zeebeClientSecret}`);
+        await (0, sessionRecovery_1.recoverStuckModelerLogin)(this.page);
         await (0, test_1.expect)(this.connectorsDocHandlingStartEventElement).toBeVisible({
             timeout: 60000,
         });

package/dist/pages/8.8/ModelerHomePage.js

@@ -282,11 +282,27 @@ class ModelerHomePage {
     // lands mid-outage used to lose the rest of its budget), and when the backend
     // stays down the wait is spent on the thing the test is actually waiting for.
     async recoverModelerSession() {
-        if (!(await (0, sessionRecovery_1.restoreSessionIfLoggedOut)(this.page))) {
+        // Two distinct ways Modeler loses its session, and only one of them shows
+        // the identity provider. When POST /api/internal/login 5xx's during the
+        // SPA's own sign-in it never logs out at all -- it parks on Modeler's
+        // /login route behind a spinner that nothing retries -- so the
+        // credentials path below cannot see it. Un-stick that first.
+        const unstuck = await (0, sessionRecovery_1.recoverStuckModelerLogin)(this.page);
+        if (!(await (0, sessionRecovery_1.restoreSessionIfLoggedOut)(this.page)) && !unstuck) {
             this.consecutiveSessionRecoveries = 0;
             return false;
         }
-        const shellVisible = await this.becameVisible(this.modelerPageBanner, 120000);
+        // Counted, not just reset: sessionDropError reports this number, and
+        // without the increment the counter read 0 forever, so the `> 0` guard at
+        // every call site was unreachable and the dropped-session diagnosis it
+        // exists to surface never once printed.
+        this.consecutiveSessionRecoveries++;
+        // The banner alone does not prove the session came back: Modeler renders
+        // its whole app shell, banner included, over the spinner on the hung
+        // /login route. Requiring the browser to have LEFT that route is what
+        // makes "recovered" mean recovered.
+        const shellVisible = !(0, sessionRecovery_1.isAtModelerLoginRoute)(this.page) &&
+            (await this.becameVisible(this.modelerPageBanner, 120000));
         if (shellVisible) {
             this.consecutiveSessionRecoveries = 0;
         }
@@ -386,6 +402,10 @@ class ModelerHomePage {
             // Reload so the check reflects the PERSISTED server state, not the
             // optimistic client render that can silently revert to "New project".
             await this.page.reload();
+            // A reload is also how the browser ends up on Modeler's hung /login, and
+            // the committed name can never render there -- which would read as "the
+            // rename did not persist" rather than "the page never loaded".
+            await (0, sessionRecovery_1.recoverStuckModelerLogin)(this.page);
             await (0, test_1.expect)(committedProjectName.first()).toBeVisible({ timeout: 15000 });
         }).toPass({ timeout: 120000 });
     }
@@ -413,6 +433,7 @@ class ModelerHomePage {
     // resource is one level down, so re-enter the container first.
     async clickProcessDiagram(name) {
         await this.ensureInResourceContainer();
+        await (0, sessionRecovery_1.recoverStuckModelerLogin)(this.page);
         const process = this.rows.filter({ hasText: name }).getByTitle(name).first();
         await (0, test_1.expect)(process).toBeVisible({ timeout: 90000 });
         await process.click();
@@ -426,6 +447,7 @@ class ModelerHomePage {
         const dropdown = this.processApplicationPage.createNewDropdown;
         for (let attempt = 0; attempt < 4; attempt++) {
             try {
+                await (0, sessionRecovery_1.recoverStuckModelerLogin)(this.page);
                 await this.dismissOverlays();
                 await (0, test_1.expect)(dropdown).toBeVisible({
                     timeout: 45000,
@@ -452,6 +474,7 @@ class ModelerHomePage {
     async clickWorkspaceDiagramTypeDropdown() {
         for (let attempt = 0; attempt < 4; attempt++) {
             try {
+                await (0, sessionRecovery_1.recoverStuckModelerLogin)(this.page);
                 await this.dismissOverlays();
                 await (0, test_1.expect)(this.diagramTypeDropdown).toBeVisible({
                     timeout: 45000,
@@ -483,7 +506,21 @@ class ModelerHomePage {
             if (await this.becameVisible(this.diagramPropertiesPanel, 1000)) {
                 return;
             }
-            if (!(await this.becameVisible(this.bpmnTemplateOption, 5000))) {
+            await (0, sessionRecovery_1.recoverStuckModelerLogin)(this.page);
+            const menuOpen = await this.becameVisible(this.bpmnTemplateOption, 5000);
+            // Hub disables this item while its own create-file request is in flight
+            // (`disabled={creatingType === BPMN}` in CreateActionDs). A request that
+            // never answers leaves it disabled for good -- yet still visible, so the
+            // probe above passed and the click below then spent its whole 30s on
+            // "element is not enabled" on every single attempt until the test timed
+            // out. Only a reload clears that React state; the menu is closed by it,
+            // which is why clickDiagramTypeDropdown has to reopen it.
+            const stuckDisabled = menuOpen &&
+                !(await this.bpmnTemplateOption.isEnabled().catch(() => false));
+            if (stuckDisabled) {
+                await this.page.reload({ waitUntil: 'domcontentloaded' });
+            }
+            if (!menuOpen || stuckDisabled) {
                 await this.clickDiagramTypeDropdown();
             }
             // 30s rather than the old 120s: the option is proven visible above, so a
@@ -493,9 +530,15 @@ class ModelerHomePage {
         }).toPass({ timeout: 240000, intervals: [1000, 2000, 5000] });
     }
     async clickFormOption() {
+        // The create menu only exists on a rendered container page. When the
+        // navigation that got us here bounced to Modeler's hung /login, this
+        // option is not merely late -- it is on a page that never renders -- so
+        // recover before spending the click budget looking for it.
+        await (0, sessionRecovery_1.recoverStuckModelerLogin)(this.page);
         await this.formTemplateOption.click();
     }
     async enterFormName(name) {
+        await (0, sessionRecovery_1.recoverStuckModelerLogin)(this.page);
         await (0, test_1.expect)(this.formNameInput).toBeVisible({ timeout: 120000 });
         await this.formNameInput.click({ timeout: 60000, force: true });
         await this.formNameInput.fill(name, { timeout: 60000 });

package/dist/pages/8.8/ProcessApplicationPage.js

@@ -3,6 +3,7 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.ProcessApplicationPage = void 0;
 const test_1 = require("@playwright/test");
 const submitModalWithRetry_1 = require("../../utils/assertionHelpers/submitModalWithRetry");
+const sessionRecovery_1 = require("../../utils/sessionRecovery");
 // Which process application holds the current test's resources, and which
 // cluster its development stage currently points at. Keyed by the Playwright
 // Page because the object that creates the container (ModelerHomePage) and the
@@ -92,6 +93,12 @@ class ProcessApplicationPage {
         return this.folderExplorer.or(this.breadcrumb).first();
     }
     async waitForProcessApplication(timeout = 90000) {
+        // Every route into this page is a navigation, and a navigation is exactly
+        // when Modeler can bounce the browser onto its own hung /login. Neither
+        // the folder explorer nor the breadcrumb can ever render there, so waiting
+        // the full timeout out first would only delay the recovery that has to
+        // happen anyway. No-ops when the page is where it should be.
+        await (0, sessionRecovery_1.recoverStuckModelerLogin)(this.page);
         await (0, test_1.expect)(this.pageReady()).toBeVisible({ timeout });
     }
     async clickCreateProcessApplicationButton() {
@@ -208,11 +215,16 @@ class ProcessApplicationPage {
             await this.page.goto(`${paUrl}/connected-clusters`, {
                 waitUntil: 'domcontentloaded',
             });
+            await (0, sessionRecovery_1.recoverStuckModelerLogin)(this.page);
             await this.openStageDefinition();
             await this.defineDevelopmentStage(clusterName);
         }).toPass({ timeout: 240000, intervals: [1000, 2000, 5000] });
         container.developmentCluster = clusterName;
         await this.page.goto(returnTo, { waitUntil: 'domcontentloaded' });
+        // Hand the caller back a page it can act on: this navigation can bounce to
+        // the hung /login just as easily as the one above, and the caller goes
+        // straight into a deploy dialog that would never open there.
+        await (0, sessionRecovery_1.recoverStuckModelerLogin)(this.page);
         return true;
     }
     // The /connected-clusters deep link opens the Define stages dialog by itself

package/dist/resources/agentic_ai/ai-agent-chat-with-tools_gemini_vertex.bpmn

@@ -43,7 +43,7 @@
             source="You are a helpful, generic chat agent which can answer a wide amount of questions based on your knowledge and an optional set of available tools.

If tools are provided, you should prefer them instead of guessing an answer. You can call the same tool multiple times by providing different input values. Don't guess any tools which were not explicitely configured. If no tool matches the request, try to generate an answer. If you're not able to find a good answer, return with a message stating why you're not able to.

If you are prompted to interact with a person, never guess contact details, but use available user/person lookup tools instead and return with an error if you're not able to look up appropriate data.

Thinking, step by step, before you execute your tools, you think using the template `<thinking><context></context><reflection></reflection></thinking>`"
             target="data.systemPrompt.prompt" />
           <zeebe:input
-            source="=&#34;Generate a single sentence in the following exact format, using Paris, France as the city and country:&#10;&#10;The current date and time in {City, Country}, is approximately {h:mm AM/PM} on {Month day, year}.&#10;&#10;But only with the sentence/format as above, nothing else&#34;"
+            source="=&#34;Generate a single sentence in the following exact format, always using a new random city and country each time:&#10;&#10;The current date and time in {City, Country}, is approximately {h:mm AM/PM} on {Month day, year}.&#10;&#10;But only with the sentence/format as above, nothing else&#34;"
             target="data.userPrompt.prompt" />
           <zeebe:input
             source="=if (is defined(followUpInput) or is defined(followUpDocuments)) then followUpDocuments else inputDocuments"

package/dist/utils/sessionRecovery.d.ts

@@ -31,3 +31,43 @@ export declare function isAtIdentityProvider(page: Page): boolean;
  * needed here.
  */
 export declare function restoreSessionIfLoggedOut(page: Page): Promise<boolean>;
+/**
+ * Whether the browser is parked on Web Modeler's OWN `/login` route, as
+ * opposed to the identity provider's login form.
+ *
+ * Two different failure states that look alike in a screenshot and need
+ * opposite recoveries, so they are kept apart deliberately. The identity
+ * provider is a separate HOST (`weblogin.`/`login.`) and wants credentials
+ * typed into it -- that is {@link restoreSessionIfLoggedOut}. This one is a
+ * PATH on the application's own host, and wants a re-navigation.
+ */
+export declare function isAtModelerLoginRoute(page: Page): boolean;
+/**
+ * Un-sticks Web Modeler when its own `/login` route has hung, and reports
+ * whether it had to.
+ *
+ * Modeler establishes its session by POSTing `/api/internal/login` from
+ * `prepareSession()`. When that call 5xx's the promise rejects and nothing
+ * catches it: `history.push(returnTo)` never runs, the app never becomes
+ * ready, and the SPA sits on `/login?returnUrl=...` rendering its shell over
+ * an infinite spinner. There is no client-side retry and no error state, so
+ * the page cannot recover on its own -- every Modeler locator the test waits
+ * for simply never appears, and the test spends its entire budget on a page
+ * that will never render. The 2026-09-22 nightly lost 22 tests across nine
+ * specs to one intermittent backend this way, each reported as an unrelated
+ * "locator not found".
+ *
+ * Reloading re-runs `prepareSession()`, so it re-issues the POST; when that
+ * one succeeds the SPA pushes the `returnUrl` it kept and the browser lands on
+ * the page the caller was navigating to. Retried because the backend fails
+ * intermittently rather than continuously -- on that nightly roughly half the
+ * calls answered 200, so a few spaced attempts are what get through. The
+ * spacing is the `waitForURL` budget itself rather than a sleep: it returns
+ * the moment the session is accepted, and otherwise spends the wait backing
+ * off.
+ *
+ * Cheap to call speculatively -- a page that is not on `/login` costs one URL
+ * comparison and no DOM access, which is what lets the Modeler page objects
+ * guard their navigations with it.
+ */
+export declare function recoverStuckModelerLogin(page: Page, attempts?: number, settleTimeout?: number): Promise<boolean>;

package/dist/utils/sessionRecovery.js

@@ -1,6 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.restoreSessionIfLoggedOut = exports.isAtIdentityProvider = exports.trackSignedInUser = void 0;
+exports.recoverStuckModelerLogin = exports.isAtModelerLoginRoute = exports.restoreSessionIfLoggedOut = exports.isAtIdentityProvider = exports.trackSignedInUser = void 0;
 // Only the username is kept -- no password, no cookie, no token. Keyed by the
 // Playwright Page because the object that logs in (LoginPage) and the objects
 // that later have to recover a dropped session (ModelerHomePage) are separate
@@ -142,3 +142,85 @@ async function restoreSessionIfLoggedOut(page) {
     return true;
 }
 exports.restoreSessionIfLoggedOut = restoreSessionIfLoggedOut;
+const LOGIN_ROUTE = /\/login\/?$/;
+/**
+ * Whether the browser is parked on Web Modeler's OWN `/login` route, as
+ * opposed to the identity provider's login form.
+ *
+ * Two different failure states that look alike in a screenshot and need
+ * opposite recoveries, so they are kept apart deliberately. The identity
+ * provider is a separate HOST (`weblogin.`/`login.`) and wants credentials
+ * typed into it -- that is {@link restoreSessionIfLoggedOut}. This one is a
+ * PATH on the application's own host, and wants a re-navigation.
+ */
+function isAtModelerLoginRoute(page) {
+    if (isAtIdentityProvider(page)) {
+        return false;
+    }
+    try {
+        return LOGIN_ROUTE.test(new URL(page.url()).pathname);
+    }
+    catch {
+        return false;
+    }
+}
+exports.isAtModelerLoginRoute = isAtModelerLoginRoute;
+/**
+ * Un-sticks Web Modeler when its own `/login` route has hung, and reports
+ * whether it had to.
+ *
+ * Modeler establishes its session by POSTing `/api/internal/login` from
+ * `prepareSession()`. When that call 5xx's the promise rejects and nothing
+ * catches it: `history.push(returnTo)` never runs, the app never becomes
+ * ready, and the SPA sits on `/login?returnUrl=...` rendering its shell over
+ * an infinite spinner. There is no client-side retry and no error state, so
+ * the page cannot recover on its own -- every Modeler locator the test waits
+ * for simply never appears, and the test spends its entire budget on a page
+ * that will never render. The 2026-09-22 nightly lost 22 tests across nine
+ * specs to one intermittent backend this way, each reported as an unrelated
+ * "locator not found".
+ *
+ * Reloading re-runs `prepareSession()`, so it re-issues the POST; when that
+ * one succeeds the SPA pushes the `returnUrl` it kept and the browser lands on
+ * the page the caller was navigating to. Retried because the backend fails
+ * intermittently rather than continuously -- on that nightly roughly half the
+ * calls answered 200, so a few spaced attempts are what get through. The
+ * spacing is the `waitForURL` budget itself rather than a sleep: it returns
+ * the moment the session is accepted, and otherwise spends the wait backing
+ * off.
+ *
+ * Cheap to call speculatively -- a page that is not on `/login` costs one URL
+ * comparison and no DOM access, which is what lets the Modeler page objects
+ * guard their navigations with it.
+ */
+async function recoverStuckModelerLogin(page, attempts = 4, settleTimeout = 25000) {
+    if (!isAtModelerLoginRoute(page)) {
+        return false;
+    }
+    for (let attempt = 1; attempt <= attempts; attempt++) {
+        console.warn(`recoverStuckModelerLogin: Modeler is stuck on ${page.url()} -- its ` +
+            `POST /api/internal/login is failing. Reload ${attempt}/${attempts}.`);
+        await page
+            .reload({ waitUntil: 'domcontentloaded', timeout: 60000 })
+            .catch(() => undefined);
+        // The reload can land on the identity provider instead -- Modeler calls
+        // Auth0 logout on some of these failures -- and there credentials, not
+        // another reload, are what gets us back.
+        await restoreSessionIfLoggedOut(page);
+        // Leaving /login is the signal that the session was accepted: the SPA only
+        // pushes the returnUrl once prepareSession() resolved.
+        const recovered = await page
+            .waitForURL((url) => !LOGIN_ROUTE.test(url.pathname), {
+            timeout: settleTimeout,
+        })
+            .then(() => true)
+            .catch(() => false);
+        if (recovered) {
+            return true;
+        }
+    }
+    console.warn('recoverStuckModelerLogin: Modeler never left /login -- its backend is ' +
+        'still failing the session call.');
+    return true;
+}
+exports.recoverStuckModelerLogin = recoverStuckModelerLogin;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camunda/e2e-test-suite",
-  "version": "0.0.1231",
+  "version": "0.0.1233",
   "description": "End-to-end test helpers for Camunda 8",
   "repository": {
     "type": "git",

package/resources/agentic_ai/ai-agent-chat-with-tools_gemini_vertex.bpmn

@@ -43,7 +43,7 @@
             source="You are a helpful, generic chat agent which can answer a wide amount of questions based on your knowledge and an optional set of available tools.

If tools are provided, you should prefer them instead of guessing an answer. You can call the same tool multiple times by providing different input values. Don't guess any tools which were not explicitely configured. If no tool matches the request, try to generate an answer. If you're not able to find a good answer, return with a message stating why you're not able to.

If you are prompted to interact with a person, never guess contact details, but use available user/person lookup tools instead and return with an error if you're not able to look up appropriate data.

Thinking, step by step, before you execute your tools, you think using the template `<thinking><context></context><reflection></reflection></thinking>`"
             target="data.systemPrompt.prompt" />
           <zeebe:input
-            source="=&#34;Generate a single sentence in the following exact format, using Paris, France as the city and country:&#10;&#10;The current date and time in {City, Country}, is approximately {h:mm AM/PM} on {Month day, year}.&#10;&#10;But only with the sentence/format as above, nothing else&#34;"
+            source="=&#34;Generate a single sentence in the following exact format, always using a new random city and country each time:&#10;&#10;The current date and time in {City, Country}, is approximately {h:mm AM/PM} on {Month day, year}.&#10;&#10;But only with the sentence/format as above, nothing else&#34;"
             target="data.userPrompt.prompt" />
           <zeebe:input
             source="=if (is defined(followUpInput) or is defined(followUpDocuments)) then followUpDocuments else inputDocuments"