Based on the behavior you're describing, it appears that the Playbook configuration may depend on values that are populated dynamically when the record is created (for example, a Parent Record or another required field). On the initial load, the script responsible for populating those values may not complete successfully, which causes the Playbook to display a configuration error. After refreshing the page, the required data is available and the Playbook loads correctly.
To confirm the exact cause in your environment, we recommend reviewing any custom client scripts, UI policies, or workspace configuration that populate required Playbook context fields during record creation.
