Lately, Viktor changed how workspaces and workers work. Each app now has a dedicated development workspace and developers can setup their own workers.
When setting up a production worker, I wanted to test if it worked so I added my Development workspace to be used with that worker. Even though the workers is listed as online, the worker is marked as Offline when I open the workspace. Is it no longer possible to connect production workers to development workspaces?
Hi Vincent,
It should still be possible to connect to your development workspace. Could you double check that you selected the correct Development workspace (attached to the right app)?
If it still doesn’t work, then we’ll do some further investigation.
Regards,
Thanks for the response. I have selected the correct workspace. The worker page says that the worker is online but when I go to the app, the worker is offline.
Hi Vincent,
Thank you for providing screenshots. I think that I’ve spotted the problem.
It seems that you also have a (Generic) Developer Worker created through your ‘My Integrations’ page in your profile settings. (I know this because in your screenshot it is listed under the ‘My Integrations’ header, instead of under ‘Organizational Integrations’) This worker always takes precedence over any Organization defined workers (even when the worker is offline; this is probably what causes the confusion here).
The easiest fix is to delete your Developer Worker through your profile settings. Then it should fall back to the Organizational Worker.
Could you check if this solves your problem?
Tip
I noticed that you are using a Generic Worker, and the description mentioned Dynamo. Have you seen that we recently added a dedicated Dynamo Worker. It works very similar to the Generic Worker implementation in terms of code, but has a simpler set-up flow and it makes the integration easier to manage. We strongly recommend using the dedicated worker for a better overall experience.
Additional info
Note, in terms of Worker priority, we have implemented the following priority system:
- Developer Worker
- Specific scoped Worker
- Global Worker
Note that this is checked per integration kind. So if you have the following three workers assigned:
- (Dev) Excel worker (automatically assigned to all your Dev Workspaces)
- (Specific) Excel worker (manually assigned to one or more Dev Workspaces)
- (Specific) Robot worker (manually assigned to one or more Dev Workspaces)
In your Integration Status in your Dev Workspace you will see:
My Integrations
Organizational Integrations
Note that, even though your (Dev) Excel worker might be offline, we do not fall back to the (Specific) Excel worker. Our reasoning:
when you are developing and you have created a Dev worker for your development, you would not want to accidentally sent a worker job to a ‘Production’ worker, simply because you forgot to start the worker.
Thanks for the info. Now the correct worker is selected 
And I am aware of the dynamo worker. We are not only using Dynamo but also FormIT together in one worker, hence the generic worker.