The Send Project Resources task will not send any resources when a resource that is not supported on edge is included. For example if a gateway script is included in the send task and compute module is not active. It will also say success when this occurs despite nothing being sent to the edge gateway.
8.1.20
Hey Michael.Smith,
Is there a reason why you are sending project resources when it's not currently supported for edge? This would help us better prioritize the bug ticket.
I do agree that "Success" in this case could be a bit more clear. Rather than saying success, it could report something along the lines of an error due to the resource not being supported.
I'll reach back out to this post once the bug ticket is filed.
This is for an EAM task. My intention is in having an include project that gets distributed to the edge server.
Edge can't do that. It supports only a single project, no inheritance.
Not in the traditional sense no, but I can set up a scheduled EAM task to send the project resources in my include project to the edge project, which allows me to synchronise it. My only problem is that it works fine if it is just basic views, but as soon as anything unsupported is included it sends nothing and still says success. It should probably send what it can and throw an error to tell me what couldn't be sent to the project. The concept of an 'include project' is irrelevant to the problem anyway, as the issue is with the EAM task, not edge limitations.
I'm not going to get a chance to test it, but I imagine this would also happen if sending a report resource from one gateway to another when the other gateway does not have the reporting module.