# Why?

## <mark style="color:red;">Important!</mark>

you switch your job using the /setjob command, and if the new job (e.g., ambulance job) has no data, the previous job’s data will still be displayed. However, if you restart your g-duty script, it will work perfectly. If the new job has data, it will work

\
⚙ <mark style="color:blue;">**Why is it not calculating?**</mark>\
This issue occurs because you are restarting the script every time or using the [<mark style="color:purple;">/setjob</mark>](#user-content-fn-1)[^1] command to switch jobs.

\
⚙ <mark style="color:blue;">**When calculating the player’s duty time**</mark> <mark style="color:blue;"></mark><mark style="color:blue;">?</mark>\
it only calculates if the player interacts with the menu and switches off duty.

⚙ <mark style="color:blue;">Failed to update player</mark> <mark style="color:blue;"></mark><mark style="color:blue;">**error notifications?**</mark>\
When `'Failed to update player'` errors appear, it's because the job does not exist to update, create `offduty` or `` onduty or `job grades` `` job in sql

[^1]: