client.workspace_busy
Local files changed underneath the client
| Type | https://mthds.ai/errors/client.workspace_busy |
| Family | client: What a client detects itself, and never receives as a response body. |
| Domain | runtime: nobody could have acted beforehand, so whoever made the call waits, retries or reports the problem |
| Retry | yes: repeating the operation may succeed, after retry_after seconds when the problem gives it |
| HTTP status | none (client) |
| Raised as | an error a client detects itself, never received from a runner |
What it means
Another process holds the lock on, or wrote, the files the call read.
What to do
Wait for the other process to finish, then try again.
Next steps
A problem carries the step aimed at whoever reads it: the first when its reader is the domain's actor, whoever made the call, and the second for any other reader.
| Reader | Kind | Detail |
|---|---|---|
| The domain's actor | retry |
Try again once the other process is done with '{path}'. |
| Any other reader | retry |
Try again once the other process is done with '{path}'. |
Detail
The problem's detail is written from this template, filled with the occurrence's parameters:
Another process holds or changed '
{path}', which this call read.
Parameters
Every parameter is present on every occurrence of the code.
| Name | Type | Description |
|---|---|---|
path |
caller_text |
The file or the directory. |
See also
- Error Registry, which describes the members of this page
- Error Codes, every code of the core registry