Why can a task disappear when you switch to another account?

Identify the submitting account from a real record

Check the signed-in account details before interpreting an empty gallery. In an illustrative stationery project, a creator used a work email yesterday and signs in with a personal account today. The personal account's empty history is expected to show its own work. It cannot establish the fate of a task submitted from the work account.

Use your own recorded account details and the submission confirmation, if available. Avoid guessing from a shared computer's remembered profile or a familiar avatar. A browser profile and an CartVisual account are different things. Confirm the website session itself, then locate the owner account through your normal sign-in process. Do not ask a collaborator to reveal credentials to make their history appear in yours.

Check the broad task list before a small gallery

Open Generation tasks and look for the product name, creation time and operation. Relevant workbench galleries can show a smaller tool-specific selection of recent work. The absence of a thumbnail there is not sufficient evidence that the overall task history lacks the request.

Then separate ongoing work from completed assets. My assets focuses on completed creations, so a queued or pending job belongs in the task investigation. A logo, video and product image can have similar campaign names while remaining different operations. Use the creation type as well as the name. If a known task is visible, follow its actual state instead of creating a duplicate just to refill the gallery.

Use an account-context decision table

The table is an investigation aid, not automatic account recovery. Keep the distinction between a server record and browser-local preparation. A draft saved in one account context or tab should not be assumed to follow every new session. If the request was never submitted, there is no missing generation for the task list to display.

Use fictional accounts Work and Personal as private labels, not real email addresses. Work’s task T8 is recorded as pending; Personal’s recent product gallery is empty. First inspect T8 in Work’s Generation tasks, not Personal’s gallery. A tool gallery can be a limited recent subset—the current commerce gallery keeps up to eight recent matching jobs—so older or other-tool work needs the broader task view. A downloaded image received by Personal does not import Work’s task history or grant access to T8.

If the browser lost the response after submission and you have only a brief, record “submission unconfirmed,” not “never submitted.” The absence of an identifier in that tab does not prove that no server request exists. Check the correct account and broader task history, then give support the time, operation and available submission evidence if it remains absent. Do not launch duplicates in several accounts to test which one owns the result. No account was switched and no task was queried for this exercise.

Treat sign-in differences as evidence to verify

Photoroom specifically warns that different sign-in methods need the same associated email to reach the same Photoroom account.

That first-party support question illustrates why a familiar sign-in button is insufficient account evidence. CartVisual's account identity must be checked in CartVisual itself; do not infer that another service's account-linking rules apply here. If an access method fails, use the site's supported recovery route for your own account rather than starting repeated new accounts to search for the result.

Keep any support note limited to the intended account, task identifier, approximate submission time and visible behavior. Passwords, recovery codes and browser authentication data are not diagnostic attachments. If you cannot establish the owner account, state that uncertainty directly instead of declaring the job deleted.

Resume the right work once the context is clear

After entering the stationery work account, suppose the task is pending. Use the existing-task status check next rather than regenerating in the personal account. If it completed, download and review its result. If it failed, read the error and associated account information before deciding on a corrected request.

If the owner account is correct but the task remains absent, report the submission evidence through Feedback. A screenshot showing an unsent brief proves a different stopping point from a task identifier. Record which one you have. For collaboration, use the manual creative handoff with authorized files; this external file handoff does not merge account histories or move the original task. Close the investigation with a clear owner and task state, or an explicit unresolved record.