Requests and publication questions
Use these answers when a change is prepared, waiting for information or not yet visible in production.
Why did the arrow not start the work?
The arrow adds a row to Studio's pending list. Review that list and click Send all to submit the batch. Read its confirmation before assuming the request has been recorded.
Check whether the row is still in the pending list above the request field or has a recorded request detail. A prepared row can still be edited or removed. A submitted request is followed from its own record and can ask for clarification before construction progresses.
Why does a pasted URL fail to choose a page?
It must identify an available page belonging to the selected project's known services. Check the full address and project, or find the existing page by name in the same field.
Use the page address from the project’s own service and confirm the suggested page before describing a change. A URL is a way to find an existing target; pasting an unknown address does not create that page or grant access to another project.
Why can I not add a different business area to the batch?
The first request fixes the batch context. Submit or remove its pending items before starting a batch for another area.
Separate the changes into batches with a coherent context. Review the first batch’s target and rows, submit or remove them, then choose the other area. This keeps each recorded change connected to the intended part of the application.
What should I do after a partial send?
Read how many requests were recorded and inspect the rows remaining in the pending list. Retry those rows; recreating requests that already succeeded produces duplicate work.
Keep the successful requests in their recorded follow-up and address only the unsent rows. Read the error or remaining context before retrying. The count in the confirmation is more useful than assuming every prepared row was either sent or rejected together.
Why is the work asking me questions?
A business rule or expected result still needs clarification. Open the question attached to that item, supply a concrete example and submit the response.
Explain the normal result and the important exception. For example, state what an approved customer may confirm and what a pending customer should see. Answer on the item that asked the question so its response remains part of the same requirement.
Why is a completed change not visible in production?
Construction completion does not publish a version. Verify the development result, create the appropriate project version, test staging and check the production version after deployment.
Check both the version and the complete journey, including the page link and the exception used in the request. A different result in another environment can come from a different publication. Identify the tested version before sending a follow-up about the same change.
Why is production deployment unavailable?
Read the prerequisite shown by Deployment. A version may need to be created, staged or verified, a required domain may be unverified, or a deployment may already be underway.
Resolve the condition shown by the current screen in its own tool. A domain check, version creation and a deployment already processing have different next actions. Repeated submission does not complete a missing prerequisite or prove that publication is finished.