Three states that should not be combined
Close Forge has a deployment state, workflow versions and messaging activity. A workflow draft can exist in a disabled deployment. A workflow can be published while its deployment remains paused. Pending work and already-sent messages have their own states.
Tell Work which level you want to change. “Save the new copy” does not mean “activate sending.” “Pause the deployment” cannot recall messages already accepted by a provider.
Inspect before configuration
Inspect the exact Close Forge deployment named Estimate check-in. Show its status, current settings and workflow versions. Explain what would change if we updated its send window; do not apply anything.
Supported configuration is reviewed against the current revision of a paused deployment. It includes its name, time zone, send window and explicit consent certification. A send-window edit can also update quiet hours and existing campaign schedules, so review more than just the displayed name.
Never certify consent merely to clear an error. Only request consent attestation after the authorized person has actually confirmed it. Connector credentials, opt-outs and platform send gates are not bypassed by a Work configuration request.
Publish the reviewed workflow
- Select the exact draft workflow and review its current version.
- Keep the deployment paused while publishing through this workflow.
- Explicitly ask to publish that draft and inspect the publication proposal.
- Approve only the intended workflow replacement. Publication compiles its campaign while retaining history; it does not itself enroll customers, replay history or send messages.
Resume for future eligible work
Ask Work to review resume consequences and readiness for the selected disabled deployment. Normal connector, sender and messaging checks still apply. Approve resume only after those prerequisites match the intended operation.
Resume permits future eligible intake. It does not recreate messages stopped by an earlier pause, activate an archived deployment or publish an unpublished workflow. Address any missing readiness in the owning app before retrying.
Pause or archive intentionally
Review the pending activity and consequences of pausing Estimate check-in. Prepare a pause only for this deployment. Preserve delivered history and tell me what cannot be recalled.
Pause stops pending future work within the reviewed scope. Archive is a separate, explicit request that also retains history but cannot be reversed through the documented Work path. Inspect the exact target and consequences before approving archive.
These lifecycle controls are specific to Close Forge. Do not assume the same command can pause every TradeVulcan app or stop live Google Ads delivery.
After an interruption
Use Refresh saved status and inspect the affected deployment. An unconfirmed provider outcome is not a safe invitation to repeat an action. Keep the saved operation reference, review current state and request help when the effect remains uncertain.