2 of my flows are continuously generating errors (see print screen in attachment). There are no files in the folders, or other files in the flow. Already did the following:
Reboot
Installed the 2019 fall edition
Checked all items and folders in the flow
Updated all the apps to the new versions
Has someone a idea how to fix this? And where I need to look to solve it? Like to hear!
Kind Regards,
Martijn
Attachments
sample-errors.PNG (72.9 KiB) Viewed 6722 times
Working with: Enfocus Switch, Pitstop Server, Quite Imposing, Kodak Nexpress (max 640mm sheets and 500grs) with most options (HD, Clear, Gold, White, Light-Black and Matt fuser), Polar Mohr D80 (compucut), Multigraf, Heidelberg, GMP, Duplo, Hohner.
Yes that should be the problem. Thanks, no solution yet I see. I trying to go back to version 3, but didn't help. I wil continue in the other post. Thanks!
Working with: Enfocus Switch, Pitstop Server, Quite Imposing, Kodak Nexpress (max 640mm sheets and 500grs) with most options (HD, Clear, Gold, White, Light-Black and Matt fuser), Polar Mohr D80 (compucut), Multigraf, Heidelberg, GMP, Duplo, Hohner.
Although it was made with a job transfer from one Switch installation to another one in mind it can also be used locally (just use the default settings).
WARNING: Switch2Switch does not support job folders.
For those who are interested in the technical details, the two Switch2Switch apps use a totally different approach: "Send to Switch" sends a webhook, and "Receive from Switch" handles the webhook by retrieving the job and its metadata from Switch's REST API. No intermediate packed file is created and it is therefore also faster than Portals. At least when you have the Switch 2019 Fall release. The REST API of the Spring release did not yet have support for requesting the private data and the datasets of the job, so you had to do "Pack job" before sending and "Unpack job" after receiving.
Although it was made with a job transfer from one Switch installation to another one in mind it can also be used locally (just use the default settings).
WARNING: Switch2Switch does not support job folders.
For those who are interested in the technical details, the two Switch2Switch apps use a totally different approach: "Send to Switch" sends a webhook, and "Receive from Switch" handles the webhook by retrieving the job and its metadata from Switch's REST API. No intermediate packed file is created and it is therefore also faster than Portals. At least when you have the Switch 2019 Fall release. The REST API of the Spring release did not yet have support for requesting the private data and the datasets of the job, so you had to do "Pack job" before sending and "Unpack job" after receiving.
Never thought of this use case for Switch2Switch, works great thank you Freddy! Was going to say the only thing that was missing was being able to set the URL and Channel variables on the properties but I've just seen that version 3.0 has that functionality.