VEC Error - Action could not be applied due to missing or invalid mbox name | Community
Skip to main content
Neelabh_
Level 2
May 2, 2022
Solved

VEC Error - Action could not be applied due to missing or invalid mbox name

  • May 2, 2022
  • 2 replies
  • 2557 views

Hi Everyone,

While trying to create an A/B test, I am trying for layout test for contents on page, by resizing container on one of the container and moving other using 'Layout' option. However any change gives me an error on modification pane as - 'Action could not be applied due to missing or invalid mbox name'.

Also I tried to go ahead and save the experience [even with error] and then test it using QA URL but just the default experience and not the test version.

Can you please help me to find the cause behind this error and fix it.

Thanks,

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Amelia_Waliany

8.31.22 Adobe Target Community Q&A Coffee Break Answer provided by @shelbygoff 

----------------------------

Hi @NeelabhParmar, thanks for your question. I've seen this error appear for a number of reasons bust mostly it has been a known UI bug. First I would ask, does this modification you make work in production? Also the Adobe Target VEC Helper Extension has been known to help clear this error. However, I would recommend opening a ticket with Adobe Target Support to troubleshoot this. 

----------------------------

Check out the entire 8.31.22 Adobe Target Community Q&A Coffee Break discussion thread for more insights on related topics 🙂 

2 replies

FelixGomez
Level 2
May 30, 2022

I have the same issue. Are you using TARGET v2?

August 4, 2022

Were you able to fix this issue and if so how?

 

Amelia_Waliany
Adobe Employee
Amelia_WalianyAdobe EmployeeAccepted solution
Adobe Employee
February 13, 2023

8.31.22 Adobe Target Community Q&A Coffee Break Answer provided by @shelbygoff 

----------------------------

Hi @NeelabhParmar, thanks for your question. I've seen this error appear for a number of reasons bust mostly it has been a known UI bug. First I would ask, does this modification you make work in production? Also the Adobe Target VEC Helper Extension has been known to help clear this error. However, I would recommend opening a ticket with Adobe Target Support to troubleshoot this. 

----------------------------

Check out the entire 8.31.22 Adobe Target Community Q&A Coffee Break discussion thread for more insights on related topics 🙂